Fact-checked by Grok 2 weeks ago

Android Jelly Bean

Android Jelly Bean is the codename given to three incremental versions of the —4.1 ( level 16), 4.2 ( level 17), and 4.3 ( level 18)—developed by and released from July 2012 to July 2013 as successors to Android 4.0 . Announced on June 27, 2012, and first released on July 9, 2012, with the Nexus 7 tablet, 4.1 emphasized smoother performance through Project Butter, which incorporated hardware-accelerated rendering, Vsync timing for consistent frame rates, and triple buffering to reduce jank in animations and scrolling. Key user-facing enhancements included expandable notifications for richer interactions without leaving the current screen, cards for proactive contextual information delivery, improved with offline capabilities, and resizable widgets. For developers, it introduced APIs for advanced notifications, the Choreographer class for precise UI timing, and peer-to-peer connectivity. Android 4.2, announced on October 29, 2012, and released on November 13, 2012, alongside the smartphone and tablet, built on 4.1 by adding multi-user support for tablets (allowing separate profiles with isolated apps and data), lock screen widgets for quick access to information, and expanded accessibility features like gesture-based navigation. Notable additions encompassed Photo Sphere for panoramic imaging, gesture typing on the keyboard, support for external displays via , and interactive screensavers. Developer tools advanced with GPU-accelerated Renderscript for computational tasks, nested Fragments for complex UIs, and multi-user APIs for app compatibility across profiles. The final iteration, Android 4.3, was announced and released on July 24, 2013, primarily as an update for existing Nexus devices, focusing on refinements like restricted user profiles for (limiting app access and content on shared tablets), (Smart) support for battery-efficient connections to wearables, and 3.0 for more advanced 3D graphics rendering in games and apps. Other improvements included auto-correction in the dialer, enhanced right-to-left support for scripts like and Hebrew, and optimizations for location services and storage management. Developers gained access to new for Bluetooth LE, a framework, and notification listener services. Overall, marked a shift toward fluid, responsive experiences on devices, laying groundwork for future enhancements in notifications, personalization, and hardware integration while maintaining for the growing of smartphones and tablets.

Development

Background and Goals

, internally versioned as Android 4.1 through 4.3, entered development following the release of Android 4.0 on October 19, 2011. This timeline reflected Google's strategy of iterative improvements rather than radical redesigns, building directly on the unified phone-tablet interface introduced in . The version was publicly announced on June 27, 2012, during the keynote at , where it was unveiled as 4.1 . The primary goals for Jelly Bean centered on resolving persistent user interface smoothness issues observed in earlier releases, such as Android 2.3 and Android 4.0 , which often suffered from stuttering animations and inconsistent frame rates. Developers aimed to achieve buttery-smooth interactions at 60 frames per second, enhancing overall responsiveness without overhauling the core architecture. Additionally, sought to mitigate Android's growing OS fragmentation—where devices ran disparate versions, complicating app compatibility and security updates—through subtle refinements that prioritized user delight and ecosystem cohesion. A key strategic objective was accelerating feature delivery to users, addressed by introducing as a separate in 4.1. This modular framework allowed core functionalities, such as location services and authentication, to update independently via the Play Store, bypassing delays from full OS upgrades and further combating fragmentation across the diverse Android device landscape.

Key Innovations

One of the cornerstone innovations in the development of Android Jelly Bean was Project Butter, a comprehensive initiative aimed at achieving consistent 60 frames per second (FPS) UI rendering to eliminate visual jank and enhance overall responsiveness. This project introduced vertical synchronization (vsync) timing synchronized across the , ensuring a consistent 16ms framerate for animations, scrolling, and transitions. Triple buffering was integrated into the to allow smoother rendering by providing additional buffers for the CPU, GPU, and display to operate in harmony, preventing frame drops during high-load scenarios. Additionally, hardware composer integration optimized composition of layers directly on the GPU, reducing CPU overhead and further contributing to fluid performance. These changes collectively reduced touch latency through CPU input boosts upon touch detection and anticipation of finger positions for the next frame redraw, marking a significant leap in Android's graphical fidelity. Another key advancement was the early integration of as an intelligent , designed to deliver contextual information proactively without explicit user queries. leveraged the —a vast database connecting entities and relationships—to power predictive cards displaying relevant details such as updates, traffic conditions, or flight statuses based on user habits and location. This integration enabled enhancements where the system could provide direct spoken answers drawn from the Knowledge Graph, alongside traditional search results, fostering a more intuitive interaction paradigm. By embedding these capabilities at the OS level during development, set the foundation for context-aware computing in mobile environments. Android Jelly Bean's development also pioneered a shift toward a modular through the introduction of , which decoupled non-core features like location APIs, maps, and authentication from the main OS image. This allowed for independent, over-the-air updates via the Play Store, enabling faster iteration on services without requiring full system upgrades or carrier approvals. By isolating these components, the improved , as updates could patch vulnerabilities swiftly, and enhanced flexibility for developers integrating Google-specific functionalities. This modular approach addressed longstanding fragmentation issues in Android ecosystems, allowing features to evolve separately from the base OS. To ensure these innovations met baseline performance standards, the Jelly Bean development process emphasized rigorous internal testing on Nexus devices, which served as reference hardware running pure Android without manufacturer customizations. Engineers optimized Project Butter and other features specifically on devices like the and the newly introduced Nexus 7 tablet, verifying 60 FPS rendering and reduced latency in real-world scenarios. This testing regimen guaranteed compatibility and performance consistency across the intended hardware baseline before broader rollout.

Release History

Android 4.1 Jelly Bean

Android 4.1 , with API level 16, was officially released to the Android Open Source Project on July 9, 2012. The update focused on delivering a stable platform following a preview version unveiled at earlier that year, emphasizing smooth performance enhancements like Project Butter for improved responsiveness. The initial rollout began with the Nexus 7 (2012) tablet, which shipped pre-loaded with Android 4.1 Jelly Bean starting July 13, 2012, after its announcement on June 27, 2012, at . Over-the-air (OTA) updates followed for other Nexus devices, including the , , and , with staggered deployment commencing on July 10, 2012, for the HSPA+ variant of the . These updates were delivered incrementally to ensure compatibility and minimize disruptions across varying device configurations. The stable build for the initial release carried the number JRO03C, corresponding to Android 4.1.1, which addressed minor issues from the preview and rolled out in July 2012. Subsequent minor updates included Android 4.1.1 build JRO03C for additional devices in July 2012, providing bug fixes for stability. In October 2012, Android 4.1.2 arrived via build JZO54K, offering further refinements such as improved audio and camera functionality on supported hardware. These point releases maintained the core 4.1 framework without introducing major new features.

Android 4.2 Jelly Bean

Android 4.2 , released on November 13, 2012, represented a mid-cycle update to the Jelly Bean platform with level 17. This version introduced incremental enhancements building on the foundation of Android 4.1, including refined notification handling while adding new user-centric features. The update was deployed initially alongside new hardware, emphasizing optimizations for tablets and improved accessibility options. The rollout expanded support to the Nexus 4 smartphone, Nexus 10 tablet, and the updated 2012 Nexus 7 model, with over-the-air (OTA) updates available for previous Nexus devices such as the original Galaxy Nexus and Nexus 7. Announced on October 29, 2012, in conjunction with the launch of the Nexus 4 and Nexus 10, the update focused on tablet-specific improvements like multi-user profiles to enable shared device usage and accessibility advancements, including gesture-based navigation and enhanced screen magnification. A notable hardware-tied feature was the introduction of Photo Sphere, a 360-degree panoramic camera mode exclusive to the Nexus 4's 8-megapixel sensor, allowing users to capture immersive images for sharing on Google+ or integration with Google Maps. Subsequent patches addressed stability and security issues, with Android 4.2.1 (build JOP40D) released in November 2012 shortly after the initial launch, followed by Android 4.2.2 (build JDQ39) in February 2013 to fix bugs like connectivity and expand device compatibility. These updates were distributed via to eligible devices, ensuring broader adoption of the refinements without requiring full hardware refreshes. The overall deployment prioritized seamless integration with the expanding ecosystem, solidifying Jelly Bean's position as a performant mobile OS at the time.

Android 4.3 Jelly Bean

Android 4.3 Jelly Bean, released on July 24, 2013, represented the final major update in the Jelly Bean series, introducing API level 18 alongside refinements to performance, security, and user management. This version built upon the multi-user capabilities introduced in Android 4.2, emphasizing stability and developer tools while preparing the platform for the transition to Android 4.4 KitKat. The update focused on incremental enhancements rather than sweeping changes, aligning with Google's strategy to refine the Jelly Bean experience before shifting to a new codename. The initial rollout targeted Google's Nexus lineup, including the Nexus 7 (both 2012 and 2013 models), Nexus 4, , and , with over-the-air () updates available for these compatible devices shortly after announcement. Factory images and OTA packages were made available on the Android Developers site to facilitate manual installations. This release coincided with the unveiling of the second-generation Nexus 7 tablet at a Google event in , marking a key moment in hardware-software integration for the ecosystem. Build JWR66Y served as the initial release for most devices, delivering the core 4.3 functionality. A subsequent minor update, Android 4.3.1 (build JLS36I, released on October 4, 2013), addressed stability issues with a small 9.4 MB package, primarily for the Nexus 7 LTE (2013) but applicable across supported hardware. This patch concluded active development for the branch, focusing on bug fixes without introducing new features. Key user-facing additions included restricted profiles, a feature extending multi-user support on tablets to create isolated accounts with customizable app and content restrictions, ideal for or shared devices. Minor tweaks accompanied this, such as improved settings navigation for user management. Developers gained access to 3.0 for advanced graphics rendering and an expanded (LE) API for better connectivity with peripherals. These changes solidified Jelly Bean's role as a stable foundation, paving the way for future iterations.

User-Facing Features

Interface and Interaction Enhancements

Android 4.1 Jelly Bean introduced Project Butter, a comprehensive optimization effort aimed at delivering a fluid experience by achieving consistent 60 frames per second () for scrolling, animations, and touch responses throughout the system. This initiative synchronized the CPU and GPU operations with vertical sync (Vsync) to prevent jank and ensure smooth rendering, fundamentally enhancing perceived responsiveness on devices like the Nexus 7 tablet. A key user-facing enhancement was the integration of , a predictive search and feature that presented information via context-aware "cards" for weather, traffic, events, and more, based on the user's location and habits. Users accessed through a simple upward swipe gesture from the bar on the , allowing seamless delivery of proactive insights without manual queries. In Android 4.2 Jelly Bean, the received significant customizations, enabling users to add widgets directly for quick glances at calendars, emails, or other apps without unlocking the device. Swiping right from the provided immediate access to the camera, streamlining photo capture while maintaining security for the rest of the interface. Android 4.2 introduced Photo Sphere, a panoramic photo capture mode in the Camera app that enables users to create 360-degree images by panning the device, with on-screen guides for alignment. Gesture typing was added to the default Android keyboard in Android 4.2, permitting users to input text by gliding a finger across letters to form words, similar to swipe-based methods but integrated natively for faster composition in messaging and search. Complementing this, Jelly Bean improved font rendering with optimizations for subpixel accuracy, particularly for thin fonts at small sizes and complex scripts like CJK, , Hebrew, Thai, and Indic languages, resulting in sharper readability across apps. Android 4.2 also debuted , an interactive screensaver mode that activated when the device was docked, charging, or idle, displaying dynamic content such as photo slideshows, clock widgets, or visualizations to transform idle time into engaging visuals. This feature extended usability for docked tablets and phones, offering customizable, low-power alternatives to a blank screen.

Notification and Accessibility Improvements

Android 4.1 introduced expandable notifications, allowing apps to display richer content such as photos, emails, or music controls directly in the shade. These notifications can be expanded or collapsed with a pinch , and users can perform actions like replying to messages or skipping tracks without opening the app. This enhancement improves user engagement by providing more context and interactivity at a glance. In Android 4.2, the notification system was further refined with the addition of a quick settings panel, accessible by swiping down from the top of the screen. This panel offers one-tap toggles for common functions, including , , brightness, and location services, streamlining device management without navigating deep into settings menus. The panel is available on both phones and tablets, promoting faster access to controls. Android 4.2 also debuted multi-user support on tablets, enabling multiple profiles with separate accounts, apps, home screens, and data. Each user maintains individual settings and app installations, while shared resources like the device's and are partitioned for . This feature enhances shared device usage in households or workplaces by isolating personal environments. Android 4.3 further enhanced multi-user capabilities with restricted profiles, enabling the creation of limited user accounts that restrict access to specific apps, settings, and in-app purchases for safer shared use, such as on tablets. Accessibility received significant expansions starting in Android 4.1, with enhancements to TalkBack, the for visually impaired users. TalkBack now includes gesture-based navigation, allowing users to explore the screen by swiping and double-tapping to activate elements, along with improved audio feedback for better orientation. These changes make the interface more navigable through touch exploration. Android 4.2 added magnification gestures, enabling users to triple-tap the screen to up to 6x and across content for low-vision . This full-screen magnification works across apps and the , with options to temporarily zoom via volume key shortcuts. Additionally, support for output was introduced through new feedback types in accessibility services, allowing compatible devices to connect to refreshable braille displays for tactile reading. These notification and accessibility features integrate with Google Now cards, which appear as expandable alerts to deliver contextual updates like weather or traffic without disrupting the user experience.

Platform and Technical Enhancements

Performance and Graphics Upgrades

Android 4.1 Jelly Bean introduced Project Butter, a set of platform optimizations aimed at delivering smoother interactions. This initiative incorporated vertical sync (vsync) timing to synchronize rendering with the display's , ensuring a consistent 16ms framerate across the framework and applications for fluid animations. Triple buffering was also implemented to reduce frame drops and enhance rendering smoothness by allowing multiple frames to be prepared simultaneously. Additionally, touch latency was minimized through CPU input boosts following periods of inactivity, contributing to more responsive gesture handling. These changes collectively targeted sub-16ms per-frame latency, enabling 60 frames per second performance in UI elements like scrolling and transitions. In 4.2 , memory management saw refinements to support efficient operation on devices with varying capacities, including optimizations for systems above 512MB through adjusted garbage-collection parameters in the Dalvik runtime. This concurrent mark-and-sweep approach reduced pauses, allowing for more aggressive background app termination on low- configurations to prevent out-of-memory conditions without compromising foreground performance. for 2D rendering, already default-enabled since Android 4.0 for compatible GPUs, was further leveraged in to offload complex drawing operations, improving overall rendering efficiency across apps. Android 4.3 Jelly Bean advanced graphics capabilities with native support for , enabling developers to utilize advanced effects, , and high-precision texture compression for enhanced 3D rendering in games and applications. This upgrade supported features like self-shadowing and detailed surface mapping on supported hardware such as the Nexus 7. Battery life received targeted enhancements, including scan-only mode to reduce power consumption during location services and hardware-accelerated geofencing as precursors to later adaptive power-saving mechanisms, alongside adaptive brightness adjustments that dynamically lowered screen intensity based on ambient light to extend usage time.

Connectivity and Security Changes

Android 4.2 introduced a completely rewritten , known as Bluedroid, developed in collaboration with to replace the previous BlueZ implementation, resulting in enhanced stability, better compatibility with accessories, and more reliable performance overall. This update addressed longstanding issues with connectivity in earlier Android versions, including intermittent disconnections and inconsistent pairing, while optimizing the for Android-specific hardware configurations. Additionally, the new stack laid the groundwork for advanced audio features, such as improved Advanced Audio Distribution Profile (A2DP) support, enabling higher-quality stereo streaming with reduced latency on compatible devices. Building on this foundation, Android 4.3 expanded Bluetooth capabilities with built-in support for (BLE) profiles, introducing standard APIs for device discovery, GATT service querying, and connection management in the central role, which facilitated low-power applications like fitness trackers and proximity sensors. This addition, available initially on devices like the Nexus 4 and Nexus 7 (2013), marked a significant step toward energy-efficient wireless interactions without compromising on range or data transfer efficiency. Furthermore, Android 4.3 added support for the AVRCP 1.3 profile, enhancing A2DP by allowing richer media controls and metadata display, such as track names and artist information, during streaming to devices. In terms of Wi-Fi enhancements, Android 4.3 introduced a scan-only mode that permitted continuous scanning for improved accuracy without requiring an active connection, thereby conserving life and serving as an early precursor to broader measures by minimizing unnecessary associations with access points. This feature complemented improved hotspot management introduced in Android 4.2, which streamlined and peer-to-peer service discovery for tasks like and printer detection, reducing setup complexity in enterprise and personal . On the security front, Android 4.3 implemented the App Ops framework, a hidden system that provided granular control over individual permissions, allowing users to revoke access to sensitive features like microphone usage, location tracking, and without disabling the entire application. Accessible via third-party tools initially, this mechanism aimed to enhance user privacy by enabling fine-tuned oversight of app behaviors, though it was later removed in Android 4.4 KitKat due to implementation complexities. Complementing this, Android 4.2 enhanced VPN capabilities, building on introduced in Android 4.0 to support enterprise VPN tunnels and isolate data flows in mixed-use environments. Device encryption received refinements across Jelly Bean versions, with Android 4.1 and 4.2 making full-disk more reliable and accessible by integrating it directly with methods like or PINs, ensuring data protection without requiring complex passwords. This built upon Android 4.0's foundational support, allowing users to encrypt the entire using their chosen —such as a 4-digit PIN or swipe —for seamless boot-time decryption while hardening against unauthorized access. In Android 4.3, further cryptographic improvements bolstered integrity for stored data and communications.

Development and APIs

New Developer APIs

Android Jelly Bean introduced several new APIs across its versions (4.1, 4.2, and 4.3), enhancing capabilities for , notifications, multi-user support, graphics rendering, and media capture to facilitate more advanced and inclusive app development. These APIs, available starting from API level 16, allowed to build richer user experiences while leveraging the platform's evolving technical foundations. In 4.1 ( ), new accessibility APIs expanded support for screen readers and gesture-based interactions through enhancements to the AccessibilityService class. These included methods for handling user gestures, such as touch exploration, and managing accessibility focus as users navigate on-screen elements and the navigation bar, enabling more precise control for services like TalkBack. Developers could now implement gesture detection via onGesture callbacks and focus management using AccessibilityNodeInfo for better integration with dynamic UI elements. Additionally, APIs for feedback and global accessibility options were introduced, allowing apps to label views more effectively and distinguish between touch exploration and custom gestures. The Choreographer class was added to enable precise synchronization of updates with the display's vertical sync (Vsync) signal, helping developers achieve smooth 60fps animations by posting callbacks at the start of each frame. (P2P) connectivity APIs, via the WifiP2pManager class, allowed direct device-to-device communication without a access point, supporting discovery, connection, and data transfer for features like or multiplayer . Notification APIs in Android 4.1 (API level 16) introduced customizable expandable views, enabling developers to create richer, multi-line notifications using styles like BigTextStyle, BigPictureStyle, and BigInboxStyle via the Notification.Builder.setStyle() method. This allowed apps to display extended content, such as long text messages or images, upon user expansion, along with support for up to three action buttons per notification to streamline interactions without leaving the notification shade. Priority channels were also added through Notification.PRIORITY_HIGH and similar constants, helping apps categorize urgent alerts for better user prioritization. In Android 4.3 (API level 18), the NotificationListenerService was introduced to let apps observe and interact with system notifications programmatically. Android 4.2 (API level 17) brought multi-user to support profile switching on tablets and shared devices, primarily through the UserManager and UserHandle classes. UserManager provides methods like getUsers() to query active users, createUser() to add new profiles, and isUserRunning(UserHandle) to check user states, enabling apps to adapt to multi-tenant environments. UserHandle represents user identifiers, allowing operations like intent targeting to specific users via Intent.addFlags(Intent.FLAG_RECEIVER_REGISTERED_ONLY) combined with user-specific extras. These facilitated secure data isolation and user-specific app behaviors, with extensions in 4.3 for restricted profiles via UserManager.setUserRestriction(). Graphics and UI enhancements in 4.2 included GPU-accelerated Renderscript for compute-intensive tasks, allowing developers to offload operations like image processing or simulations to the GPU via the class and intrinsics for faster performance on supported hardware. Nested Fragments support was added, enabling developers to embed Fragments within other Fragments for more modular and dynamic user interfaces, using FragmentTransaction.add(parentId, childFragment) to build complex layouts. Media framework updates introduced the Photo Sphere capture API, enabling 360-degree image creation through extensions to the class. Developers could implement panoramic stitching using Camera.Parameters for preview configuration with spherical projections. For graphics, Android 4.3 (API level 18) added 3.0 APIs, providing advanced rendering capabilities through the GLES30 class in the javax.microedition.khronos.opengles package. Key features include vertex shader extensions for compute shaders, high-quality ETC2/EAC texture compression, and improved debug tools like GL_KHR_debug for error reporting, allowing developers to create more performant 2D and 3D visuals with features such as uniform buffer objects and instanced rendering. Apps could query support via GLES30.glGetString(GLES30.GL_VERSION) and access these via native NDK bindings for high-performance scenarios. Media enhancements continued with the addition of MediaMuxer for multiplexing audio and video streams into container formats like MP4, supporting encoding and integration with Camera2 for advanced output handling in panoramic and other apps.

Tools and Ecosystem Changes

A key ecosystem shift in Android Jelly Bean came with the introduction of version 1.0 in September 2012, coinciding with 4.1 ( level 16). This independent, updatable library decoupled Google-specific features from the core platform, enabling faster iteration on services like location APIs, integration, and (GCM) for push notifications without requiring full OS updates. Developers could thus leverage these capabilities on Jelly Bean devices while ensuring compatibility through over-the-air updates to the Play Services , reducing reliance on fragmented device manufacturer implementations. To address Android's growing fragmentation—where diverse hardware and delayed OS updates hindered app consistency—Google enhanced the Android Support Library during the Jelly Bean era (API levels 16–18). Originally launched as the Compatibility Library in 2011, it received updates to backport modern features such as Fragments, the ActionBar, and loader components to devices running 2.3 (API level 9) and above, allowing developers to deliver uniform functionality and UI behaviors across older versions without native platform support. This approach minimized compatibility issues, as apps could use the library's stable s to target a broader ecosystem while itself emphasized performance optimizations like Project Butter's 60fps rendering. SDK tools evolved significantly to support Jelly Bean development. With Android Development Tools (ADT) 21.0 in November 2012 for 4.2 ( level 17), the layout editor gained multi-configuration previews, enabling designers to prototype UIs across orientations, screen sizes, and locales directly within , which streamlined adaptation to Jelly Bean's expanded and notification capabilities. The improved via a redesigned Android Virtual Device (AVD) manager, simplifying creation of profiles mimicking real devices like the Nexus 7, and integrating AVD previews into the layout editor for real-time testing. Earlier, SDK Tools revision 20 (June 2012) for 4.1 introduced Systrace for tracing system and app performance, complementing Hierarchy Viewer enhancements that better handled hardware-accelerated view hierarchies under Project Butter, aiding debugging by revealing overdraw and layout inefficiencies in smooth animations. These tools, tied to levels 16–18, boosted productivity amid Jelly Bean's focus on refined graphics and input responsiveness. App distribution mechanisms advanced with in-app billing version 2, launched in May 2012 ahead of 's full rollout, introducing subscription support including free trials and improved purchase flows for managed products. This update, integrated via , allowed apps to implement recurring revenue models more seamlessly, with APIs for querying subscriptions and handling renewals independently of the billing library's core version. Complementing this, a preview of Game Services emerged in May 2013, offering to APIs for achievements, leaderboards, and cloud saves within the Play Services framework, enabling game developers to enhance social and progression features on devices before the full launch.

Adoption and Legacy

Device Support and Market Adoption

Android Jelly Bean was designed to run on devices with a minimum of 512 MB of RAM, though optimal performance was achieved on hardware with 1 GB or more, leading some manufacturers like HTC to exclude lower-RAM models from updates. The operating system primarily supported Google's Nexus lineup, with the Nexus 7 (2012) launching alongside Android 4.1 in July 2012, followed by the Nexus 4 and Nexus 10 debuting with Android 4.2 in November 2012. Select devices from other original equipment manufacturers (OEMs) also received Jelly Bean updates, including the Samsung Galaxy S III, which shipped with Android 4.1, and the Motorola Droid Razr Maxx HD. OEMs often customized Jelly Bean with proprietary user interfaces, or "skins," that modified core features for brand differentiation; for example, Samsung's overlaid additional widgets, animations, and app integrations on the Galaxy S III, altering the stock experience. These variations contributed to ecosystem diversity but also introduced inconsistencies in feature availability and performance across devices. Update distribution faced significant challenges due to carrier approvals and manufacturer priorities, exacerbating Android fragmentation as many eligible devices remained on older versions like Ice Cream Sandwich for months. Initial adoption was modest, with Jelly Bean reaching approximately 10% of active Android devices by early 2013, reflecting delays in over-the-air rollouts. Usage grew steadily thereafter, surpassing 37.9% by July 2013 and peaking at around 59% in early 2014 as more OEMs pushed updates and new devices shipped with the OS. By mid-2014, as gained traction, Jelly Bean's market share began declining, falling below 60% within months and continuing to drop with subsequent releases. It reached about 3% by 2019 and less than 0.1% by 2025, according to distribution data from and analytics firms, highlighting the rapid evolution of the ecosystem.

End of Support and Impact

Official support for Android Jelly Bean concluded with the release of version 4.3 in July 2013, after which ceased providing OS-level updates and security patches for API levels 16 through 18 on most devices. Although informal patches for specific components like continued until early 2015, the core platform received no further official maintenance beyond 2013, leaving it exposed to emerging threats without remediation. support, which extended some functionality and security features independently of the OS, ended in August 2021 with the final update to version 21.30.99. Post-2013, devices running became highly vulnerable to exploits targeting unpatched components, such as cryptographic signature flaws (e.g., CVE-2013-4787) and VPN weaknesses identified in 2014. Without updates for 18, these systems faced ongoing risks from and remote code execution. Enterprise environments also suffered, as unpatched installations amplified attack surfaces, prompting recommendations for or replacement to mitigate risks. Jelly Bean's legacy profoundly shaped Android's evolution, with its Project Butter initiative establishing the 60 FPS rendering standard for fluid user interfaces, a carried forward in subsequent releases like KitKat and beyond. This smoothness focus paved the way for KitKat's paradigm, which built on Jelly Bean's Holo foundations while addressing fragmentation through streamlined APIs and better hardware compatibility requirements. Later versions implemented fragmentation mitigations, such as mandatory update policies and runtime feature detection, in response to the ecosystem divides exacerbated during Jelly Bean's era. Criticisms of Jelly Bean centered on its handling of privacy features, notably the introduction of App Ops in version 4.3.2—a granular permission manager that allowed users to revoke specific app accesses without uninstalling. However, Google removed App Ops in Android 4.4 KitKat, citing developer compatibility issues, which ignited widespread privacy debates and accusations of prioritizing ecosystem growth over user control. The version's adoption, peaking below 60% of active devices by mid-2014, further underscored systemic update fragmentation, as carrier and manufacturer delays left many users on vulnerable builds and highlighted the need for reformed distribution models in future Android iterations. By 2025, Jelly Bean's market share has dwindled to approximately 0.04% of active Android devices, rendering it obsolete for everyday use amid dominance by versions 13 and later. Nonetheless, it retains niche relevance in , where emulators in tools like enable testing of legacy applications incompatible with modern APIs, ensuring for enterprise migrations and archival purposes.

References

  1. [1]
    Jelly Bean - Android Developers
    May 20, 2024 · Welcome to Android 4.3, a sweeter version of Jelly Bean! Android 4.3 includes performance optimizations and great new features for users and developers.
  2. [2]
    Official Android Blog
    **Summary of Android 4.1 Jelly Bean from https://android.googleblog.com/2012/06/jelly-bean.html:**
  3. [3]
    https://developer.android.com/about/versions/android-4.1
  4. [4]
    Android 4.2 APIs  |  Android Developers
    ### Summary of Android 4.2 Jelly Bean
  5. [5]
    Introducing Android 4.3, a sweeter Jelly Bean
    an upgrade to Jelly Bean that introduces a number of new features, including restricted profiles. Android ...Missing: announcement | Show results with:announcement
  6. [6]
    https://developer.android.com/about/versions/android-4.3
  7. [7]
    The (updated) history of Android - Ars Technica
    Oct 31, 2016 · ... Jelly Bean brought Android a lot closer to iOS' smoothness. ... Google Play Services—fragmentation and making OS versions (nearly) obsolete.
  8. [8]
    Android @ I/O: the playground is open
    Jun 27, 2012 · Today, we're rolling out a new version of Android called Jelly Bean, adding more entertainment to Google Play, and introducing two powerful ...Introducing Google Now · Google Play: More... · Introducing Nexus 7<|control11|><|separator|>
  9. [9]
    Android 4.1 Jelly Bean: faster, smoother, more delightful
    Jun 27, 2012 · Google announced Android 4.1 at Google I/O today. With "Project Butter," the operating system has become faster and smoother, with an emphasis on smooth ...
  10. [10]
    Official Android Blog: Android @ I/O: the playground is open
    Jun 27, 2012 · Google can speak back to you, delivering a precise answer, powered by the Knowledge Graph, if it knows one, in addition to a list of search ...
  11. [11]
    Overview of Google Play services - Google for Developers
    Google Play services powers a broad set of SDKs on Android for building your app, enhancing privacy and security, engaging users, and growing your business.Missing: introduction Jelly Bean
  12. [12]
    Codenames, tags, and build numbers - Android Open Source Project
    The build ID provides information such as the platform release, code branch, and date the release was branched from or synced with the development branch. Note: ...
  13. [13]
    Introducing Android 4.1 (Jelly Bean) preview platform, and more
    Jun 27, 2012 · We'll be releasing a final platform in a few weeks that you should use to build and publish applications for Android 4.1. For Android devices ...
  14. [14]
    Android 4.1 Jelly Bean: everything you need to know - The Verge
    Jun 27, 2012 · Google has announced that Android 4.1, Jelly Bean, will be rolled out to the Galaxy Nexus, Motorola Xoom, and Nexus S via an over-the-air update in mid-July.
  15. [15]
    [Update: Now With yakju] How-To - Android Police
    Jul 11, 2012 · Following yesterday's Jelly Bean AOSP invasion, the HSPA+ Galaxy Nexus is now receiving the release build 4.1.1 (JRO03C) of Jelly Bean.
  16. [16]
    Download: Android 4.1.2 JZO54K Update for Nexus 7 - Droid Life
    Oct 9, 2012 · Download: Android 4.1.2 JZO54K Update for Nexus 7 ... If you want to flash this file, you will need to be on build JRO03D, which was released back ...
  17. [17]
    Nexus: The best of Google, now in three sizes
    Oct 29, 2012 · Today, we're excited to announce three great new Nexus devices … in small, medium and large. And they all run Android 4.2, a new flavor of Jelly ...
  18. [18]
    Android 4.3 Available Today For Nexus 7, Nexus 4 ... - TechCrunch
    Jul 24, 2013 · Android 4.3 Available Today For Nexus 7, Nexus 4, Nexus 10 And Galaxy Nexus ... Android 4.3 will still be called 'Jelly Bean'. Darrell ...
  19. [19]
    Android 4.3 Jelly Bean official: shipping with new Nexus 7, available ...
    Jul 24, 2013 · Android 4.3 Jelly Bean official: shipping with new Nexus 7, available OTA for select devices today. Sarah Silbert. Updated Wed, July 24, 2013 at ...
  20. [20]
    Android 4.3.1 Now Rolling Out to Nexus 7 LTE (2013) as Build JLS36I
    Oct 4, 2013 · Wake up to find an Android 4.3.1 update showing as available on your Nexus 7 LTE (2013). The update is a 9.4MB file that jumps the N7 LTE up to build JLS36I.
  21. [21]
    Introducing Android 4.2, A New and Improved Jelly Bean
    Nov 13, 2012 · Today we are making Android 4.2 (Jelly Bean) SDK platform available for download. Below are some of the highlights of Android 4.2, API level 17.
  22. [22]
    Daydream: Interactive Screen Savers - Android Developers Blog
    Dec 27, 2012 · Daydream, new in Android 4.2, brings this kind of laid-back, whimsical experience to Android phones and tablets that would otherwise be sleeping.
  23. [23]
    Hardware acceleration | App quality - Android Developers
    Jan 3, 2024 · Hardware acceleration is enabled by default if your Target API level is >=14, but can also be explicitly enabled. If your application uses only ...Missing: Jelly Bean
  24. [24]
    What is BlueDroid? Android Bluetooth Stack ... - Electronics Weekly
    Jan 8, 2014 · Android 4.2 (Jelly Bean II) saw big changes to Android's Bluetooth subsystems, with a complete rewrite of the platform's Bluetooth stack.
  25. [25]
    Bluetooth Low Energy - Android Open Source Project
    Oct 9, 2025 · Bluetooth Low Energy (BLE), available in Android 4.3 and higher, creates short connections between devices to transfer bursts of data. BLE ...
  26. [26]
    App Ops: Android 4.3's Hidden App Permission Manager, Control ...
    Jul 25, 2013 · Android 4.3 has a hidden feature! It's called "App Ops" and it lets you selectively disable some permissions for your apps.<|separator|>
  27. [27]
    App Ops - what you need to know - Android Authority
    Dec 16, 2013 · App Ops is a framework inside Android which allows the permissions of individual apps to be tweaked.
  28. [28]
    VPN | Connectivity - Android Developers
    Jan 3, 2024 · Per-app VPN. VPN apps can filter which installed apps are allowed to send traffic through the VPN connection. You can create either an ...
  29. [29]
    Jelly Bean beefs up Android security - PhoneArena
    Jul 17, 2012 · According to the changelog we saw yesterday, the only mention of a security update was that "device encryption" has been made "more reliable".<|separator|>
  30. [30]
    Notification | API reference | Android Developers
    Android API Reference. Overview. Android Platform. Packages. API level. REL, 36.1, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18 ...
  31. [31]
    UserHandle | API reference - Android Developers
    Android API Reference. Overview. Android Platform. Packages. API level. REL ... UserManager · VibrationAttributes · VibrationAttributes.Builder · VibrationEffect ...Missing: 4.2 Multi-
  32. [32]
    OpenGL ES | Views - Android Developers
    Jun 18, 2024 · OpenGL ES 3.0 is supported with Android 4.3 (API level 18) and higher, on devices that provide an implementation of the OpenGL ES 3.0 API.Missing: Jelly Bean
  33. [33]
    Support Library Features Guide - Android Developers
    Feb 24, 2021 · The Support Libraries provide a wide range of classes for building apps, from fundamental app components, to user interface widgets, to media handling, to TV ...
  34. [34]
    Android SDK Tools, Revision 21
    Nov 14, 2012 · For a complete list of what's new, see the release notes for SDK Tools R21, ADT 21.0.0 and Android NDK R8c. Join the discussion on · +Android ...Missing: Jelly Bean
  35. [35]
    Android SDK Tools, Revision 20 - Android Developers Blog
    Jun 28, 2012 · Systrace for Jelly Bean and above lets you easily optimize your app. You can capture a slice of system activity plus additional information ...
  36. [36]
    HTC hangs up on Jelly Bean for phones with 512MB of RAM
    Nov 12, 2012 · The upgrade path to Android 4.1 Jelly Bean has been rocky for many. ... RAM or less will not be upgraded to Android 4.1. The FAQ indicates ...
  37. [37]
    HTC requires more than 512MB of RAM for Jelly Bean updates, One ...
    Nov 13, 2012 · HTC requires more than 512MB of RAM for Jelly Bean updates, One V and Desire C to stay on ICS · Terms and Privacy Policy · Privacy Dashboard ...
  38. [38]
    Nexus 4, Nexus 7, and Nexus 10 Announced with Android 4.2
    Oct 29, 2012 · Google has an Android 4.2 device in every size with the 4-inch Nexus 4 phone, 7-inch Nexus 7 tablet, 10-inch Nexus 10 tablet.Missing: launch | Show results with:launch<|separator|>
  39. [39]
    Best Android Jelly Bean smartphones you can get now - CNET
    Jan 15, 2013 · Take a look at this stellar list of smartphones that all offer a state-of-the-art Android experience. From the pure flavor only a true Nexus ...
  40. [40]
    Android skins: What you should know - CNET
    Aug 13, 2014 · What you're seeing is a custom "skin" that original equipment manufacturers (OEMs) create to run on top of the Android operating system.
  41. [41]
    What's the Point of Android Skins? - Gizmodo
    Dec 5, 2012 · There's Samsung's TouchWiz, Motorola's MotoBlur, HTC's Sense, and others. These customizations have come to be known as skins. Skins are a ...
  42. [42]
    What happened to the Android Update Alliance? - Ars Technica
    Jun 27, 2012 · Fragmentation on the Windows Phone platform isn't as much of a problem as it is in Android because you're still talking about a relatively small ...
  43. [43]
    Is Android fragmentation over with Jelly Bean's rise? Nope - CNET
    Jul 12, 2013 · Is Android fragmentation over with Jelly Bean's rise? Nope ; introduced Android 4.0, aka Ice Cream Sandwich, in late 2011, then refined it with ...
  44. [44]
    Jelly Bean is on 10 percent of Android devices after six months
    Jan 3, 2013 · Jelly Bean passed the 10 percent mark a couple of months earlier than Ice Cream Sandwich, which officially did so around the launch of the Nexus ...Missing: 58%
  45. [45]
    Jelly Bean Tips Past Majority Adoption Among Android Users With ...
    Jul 8, 2013 · Jelly Bean has been approaching a majority share, but this is the first time it has passed it, thanks to a 32.3 percent share for versions 4.1.X ...Missing: 10.5% September 2012
  46. [46]
    Google Android Market 2014: Jelly Bean Leads With 59.1% Share
    Jan 14, 2014 · Android version 4.1 to 4.3 Jelly Bean has acquired the maximum share which is 59.1 percent of the total Android market share.<|separator|>
  47. [47]
    Android KitKat Hits 13.6% Adoption, Jelly Bean Falls Below 60%
    Jun 5, 2014 · Android KitKat hits 13.6% adoption, Jelly Bean falls below 60% and Gingerbread slips under 15%. June 5, 2014 - 12:31 am.
  48. [48]
    Google finally updates Android distribution dashboard, Pie passes ...
    May 7, 2019 · Android 4.1/4.2/4.3 Jelly Bean (July 2012, November 2012, and July 2013): Down 1.8 points to 3.0% Android 4.0 Ice Cream Sandwich (December 2011 ...Missing: market | Show results with:market
  49. [49]
    Google No Longer Provides Patches for WebView Jelly Bean and ...
    Jan 11, 2015 · Google's reasoning for this policy shift is that they "no longer certify 3rd party devices that include the Android Browser," and "the best way ...
  50. [50]
    Google Play services discontinuing updates for Jelly Bean (API ...
    Jul 8, 2021 · For devices running JB, Google will no longer update the Play Services APK beyond version 21.30.99, scheduled for the end of August 2021.Missing: introduction modular
  51. [51]
    CVE-2013-4787 Detail - NVD
    Jul 9, 2013 · Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows attackers to execute arbitrary code.
  52. [52]
    Android's Jelly Bean, Kit Kat under cyber threat: CERT-In - ET CIO
    Mar 2, 2014 · Android's Jelly Bean, Kit Kat under cyber threat: CERT-In. A "critical flaw" has been detected in the virtual private network offered by Android ...
  53. [53]
    Popular Android IoT Apps under Security Scrutiny - PMC - NIH
    4.1. Network Security and Certificates. A vulnerability, which roots in improper signature usage, is well-known as Janus (CVE-2017-13156).
  54. [54]
    [PDF] Mobile Security: The Single Biggest Cyber Vulnerability - Zimperium
    Mobile devices are vulnerable due to lack of security, circumventing controls, and being a blind spot for IT, with no on-board sensors to detect threats.
  55. [55]
    Getting To Know Android 4.1, Part 3: Project Butter - How It Works ...
    Jul 12, 2012 · The VSync pulse is now used to start all the processing for the next frame. Most Android displays run at or around 60 frames per second (or 60 ...Missing: hardware composer
  56. [56]
    Google Removes Vital Privacy Feature From Android, Claiming Its ...
    Dec 12, 2013 · The disappearance of App Ops is alarming news for Android users. The fact that they cannot turn off app permissions is a Stygian hole in the ...
  57. [57]
    Google removes 'awesome' but unintended privacy controls in ...
    Dec 16, 2013 · Google's recent update Android 4.4.2 didn't bring many changes, but it did break off a privacy feature that slipped into KitKat by accident.Missing: debates | Show results with:debates
  58. [58]
    Android Version Market Share Worldwide | Statcounter Global Stats
    ### Summary of Android Jelly Bean Market Share (Oct 2024 - Oct 2025)