Android Marshmallow

Android Marshmallow (codenamed Android M during development) is the sixth major version of the Android operating system developed by Google, being the successor to Android Lollipop. It was announced at Google I/O on May 28, 2015, and released the same day as a beta, before being officially released on September 29, 2015. It was succeeded by Android Nougat on August 22, 2016.[5]

Android Marshmallow
Version of the Android operating system
Screenshot
Android Marshmallow (AOSP) home screen on the Nexus 5 (AVD Emulator)
DeveloperGoogle
General
availability		September 29, 2015 (2015-09-29)[1][2]
Final release6.0.1_r81 (MOI10E)[3] / October 1, 2017 (2017-10-01)[4]
Kernel typeMonolithic Kernel (Linux Kernel)
Preceded byAndroid 5.1.1 "Lollipop"
Succeeded byAndroid 7.0 "Nougat"
Official websitewww.android.com/versions/marshmallow-6-0/
Support status
Unsupported since August 2018

Android Marshmallow primarily focuses on improving the overall user experience of its predecessor. It introduced a new opt-in permissions architecture, new APIs for contextual assistants (first used by a new feature "Now on Tap" to provide context-sensitive search results), a new power management system that reduces background activity when a device is not being physically handled, native support for fingerprint recognition and USB-C connectors, the ability to migrate data and applications to a microSD card, and other internal changes.

Android Marshmallow was met by low adoption numbers, with 13.3% of Android devices running Marshmallow by July 2016.[6] Usage of Marshmallow steadily increased since then, and by August 2017, 35.21% of Android devices ran Marshmallow, before receding. As of May 2023, 1.64% of Android devices ran Marshmallow.[7] Security updates for Marshmallow ended in October 2017.

History
Further information: Android version history § Android 6.0 Marshmallow

Android Marshmallow internally codenamed "Macadamia Nut Cookie".[8] The first developer preview build for Marshmallow, codenamed Android "M", was unveiled and released at Google I/O on May 28, 2015, for the Nexus 5 and Nexus 6 smartphones, the Nexus 9 tablet, and the Nexus Player set-top box.[9][10][11] The second developer preview was released on July 9, 2015,[12][13] and the third and final preview was released on August 17, 2015, along with announcing that Android M would be titled Android "Marshmallow".[14][15]

On September 29, 2015, Google unveiled launch devices for Marshmallow: the LG-produced Nexus 5X, the Huawei-produced Nexus 6P,[16][17][18] alongside Google's own Pixel C tablet.[19][20]

Android 6.0 updates and factory images for Nexus 5, 6, 7 (2013), 9, and Player were released on October 5, 2015.[21] Older Nexus devices, including the Nexus 4, Nexus 7 (2012) and Nexus 10, did not receive an official update.[22] On October 14, 2015, LG announced that it planned to release Marshmallow for its flagship LG G4 smartphone in Poland the following week, marking the first third-party device to receive an update to Marshmallow.[23][24]

Android 6.0.1, a software patch featuring security fixes, support for Unicode 8.0 emoji (although without supporting skin tone extensions for human emoji), and the return of the "until next alarm" feature in Do Not Disturb mode, was released on December 7, 2015.[25][26][27]

System features

User experience

A new "Assist" API allows information from a currently opened app, including text and a screenshot of the current screen, to be sent to a designated "assistant" application for analysis and processing. This system is used by the Google Search app feature "Google Now on Tap", which allows users to perform searches within the context of information currently being displayed on-screen. While the "Home" button was used in Android 5 to show available apps, the "Home" button is used now (together with a voice command) to generate on-screen cards which display information, suggestions, and actions related to the content.[28] "Direct Share" allows Share menus to display recently used combinations of contacts and an associated app as direct targets.[28]

Adoptable storage

The new "Adoptable storage" feature allows a newly-inserted SD card or other secondary storage media to be optionally designated as "internal" rather than "portable" storage.

"Portable" storage is the default behavior used in previous Android versions, treating the media as a secondary storage device for storage of user files, and the storage media can be removed or replaced without repercussions, but user-installed apps are restricted to writing to their respective package name directories located inside Android/data. This restriction was introduced in Android 4.4 KitKat. The Storage Access Framework, through which shared writing access to memory cards has been reinstated in Android 5.0 Lollipop, is backwards-incompatible and slower due to latencies.[29]

When designated as "Internal" storage, the storage media is reformatted with an encrypted ext4 file system, and is "adopted" by the operating system as an extension of the primary storage partition. Existing data (including applications and "private" data folders) are migrated to the external storage, and normal operation of the device becomes dependent on the presence of the media. Apps and operating system functions will not function properly if the adopted storage device is removed, and the card can not be reused in other devices until reformatted. If the user loses access to the storage media, the adopted storage can be "forgotten", which makes the data permanently inaccessible.[28] Samsung and LG have, however, removed the ability to use an SD card as "internal" storage on their Galaxy S7 and G5 devices, with Samsung arguing that the feature could result in unexpected losses of data, and prevents users from being able to transfer data using the card.[30][31]

Platform

Android Marshmallow introduces a redesigned application permissions model; apps are no longer automatically granted all of their specified permissions at installation time. An opt-in system is now used, in which users are prompted to grant or deny individual permissions (such as the ability to access the camera or microphone) to an application when they are needed for the first time. Applications remember the grants, which can be revoked by the user at any time.[10][32][33] The new permissions model is used only by applications developed for Marshmallow using its software development kit (SDK), and older apps will continue to use the previous all-or-nothing approach. Permissions can still be revoked for those apps, though this might prevent them from working properly, and a warning is displayed to that effect.[34][35]

Marshmallow introduces new power management schemes known as "Doze" and "App Standby"; when running on battery power, a device will enter a low-power state if it is inactive and not being physically handled. In this state, network connectivity and background processing are restricted, and only "high-priority" notifications are processed.[28] Additionally, network access by apps is deferred if the user has not recently interacted with the app.[36] Apps may request a permission to exempt themselves from these policies, but will be rejected from Google Play Store as a violation of its "Dangerous Products" policy if their core functionality is not "adversely affected" by them.[36][37]

Android Marshmallow provides native support for fingerprint recognition on supported devices via a standard API, allowing third-party applications to implement fingerprint-based authentication. Fingerprints can be used for unlocking devices and authenticating Play Store and Google Pay purchases. Android Marshmallow supports USB-C, including the ability to instruct devices to charge another device over USB. Marshmallow also introduces "verified links" that can be configured to open directly in their specified application without further user prompts.[10][9] User data for apps targeting Marshmallow can be automatically backed up to Google Drive over Wi-Fi. Each application receives up to 25 MB of storage, which is separate from a user's Google Drive storage allotment.[28]

As of Marshmallow, the Android Compatibility Definition Document contains new security mandates for devices, dictating that those that are capable of accessing encrypted data without affecting performance must enable secure boot and device encryption by default.[38] These conditions comprise part of a specification that must be met in order to be certified for the operating system,[38] and be able to license Google Mobile Services software.[39] The requirement for mandatory device encryption was originally intended to take effect on Lollipop, but was delayed due to performance issues.[38]

See also

References
  1. "Refs/Tags/Android-6.0.0_r1 - platform/System/Core - Git at Google".
  2. Rakowski, Brian (October 5, 2015). "Get ready for the sweet taste of Android 6.0 Marshmallow". Official Android Blog. Retrieved March 6, 2017.
  3. "Android Source". Google Git. Retrieved October 3, 2017.
  4. "Codenames, Tags, and Build Numbers".
  5. Burke, Dave (August 22, 2016). "Taking the final wrapper off of Android 7.0 Nougat". Retrieved December 15, 2022.
  6. Chokkattu, Julian; Pelegrin, William (July 12, 2016). "Android Marshmallow's adoption rate rises to 13.3 percent". Digital Trends. Retrieved December 15, 2022.
  7. "Mobile & Tablet Android Version Market Share Worldwide". StatCounter Global Stats. Retrieved August 12, 2021.
  8. "Google's Internal Code Name For Android M Is Macadamia Nut Cookie (MNC)". May 23, 2015.
  9. Seifert, Dan (May 28, 2015). "Google announces Android M, available later this year". The Verge. Vox Media. Retrieved March 6, 2017.
  10. Chester, Brandon (May 28, 2015). "Google Announces Android M At Google I/O 2015". AnandTech. Purch Group. Retrieved March 6, 2017.
  11. Cunningham, Andrew (May 28, 2015). "Google's Android M preview build will run on the Nexus 5, 6, 9, and Player [Updated]". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  12. Kumparak, Greg (July 9, 2015). "Google Releases A Second Build Of Android M Just For Developers". TechCrunch. AOL. Retrieved March 6, 2017.
  13. Amadeo, Ron (July 9, 2015). "Google releases the second Android M Developer Preview". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  14. Eason, Jamal (August 17, 2015). "Develop a sweet spot for Marshmallow: Official Android 6.0 SDK & Final M Preview". Android Developers Blog. Retrieved March 6, 2017.
  15. Welch, Chris (August 17, 2015). "Android M's name is Marshmallow, and it's version 6.0". The Verge. Vox Media. Retrieved March 6, 2017.
  16. Kastrenakes, Jacob (September 29, 2015). "Google Nexus 6P with 5.7-inch display announced starting at $499". The Verge. Vox Media. Retrieved March 6, 2017.
  17. Savov, Vlad (September 29, 2015). "Nexus 5X announced with Android Marshmallow and Nexus Imprint". The Verge. Vox Media. Retrieved March 6, 2017.
  18. Amadeo, Ron (September 29, 2015). "Google announces the LG Nexus 5X and Huawei Nexus 6P; pre-orders start today". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  19. Chester, Brandon (September 29, 2015). "Google Announces The Pixel C Tablet". AnandTech. Purch Group. Retrieved March 6, 2017.
  20. Lomas, Natasha (September 29, 2015). "Google Announces Pixel C Android Tablet With Magnetic Keyboard Add-on". TechCrunch. AOL. Retrieved March 6, 2017.
  21. Welch, Chris (October 5, 2015). "Android 6.0 Marshmallow is now available for Google's Nexus devices". The Verge. Vox Media. Retrieved March 6, 2017.
  22. Whitwam, Ryan (September 28, 2015). "Android Marshmallow Will Begin Rolling Out To The Nexus 5, 6, 7 (2013), 9, And Player On October 5th, Along With AOSP". Android Police. Retrieved March 6, 2017.
  23. Byford, Sam (October 14, 2015). "LG begins rolling out Android 6.0 Marshmallow to the G4 next week". The Verge. Vox Media. Retrieved March 6, 2017.
  24. Nickinson, Phil (October 14, 2015). "LG announces its first Android 6.0 Marshmallow update". Android Central. Mobile Nations. Archived from the original on March 7, 2017. Retrieved March 6, 2017.
  25. Ruddock, David (December 7, 2015). "Android 6.0.1 Factory Images Now Available, Many New Emoji And December Security Patch In Tow". Android Police. Retrieved March 6, 2017.
  26. Amadeo, Ron (December 7, 2015). "Android 6.0.1 adds a ton of new emoji, and we've got the full list". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  27. R., Ben (December 7, 2015). "Android 6.0.1 Marshmallow roll-out brings 200+ emoji to Nexus devices". PhoneArena. Retrieved March 6, 2017.
  28. Amadeo, Ron (October 5, 2015). "Android 6.0 Marshmallow, thoroughly reviewed". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  29. "Scoped Storage in Android Q forces developers to use SAF". xda-developers. May 31, 2019.
  30. Amadeo, Ron (February 24, 2016). "The LG G5 and Galaxy S7 won't support Android 6.0's adoptable storage". Ars Technica. Condé Nast. Retrieved March 6, 2017.
  31. Triggs, Robert (February 24, 2016). "LG G5 and Galaxy S7 don't support Marshmallow's adoptable storage". Android Authority. Retrieved March 6, 2017.
  32. Mediati, Nick (October 12, 2015). "How to toggle app permissions in Android Marshmallow". Greenbot. International Data Group. Archived from the original on March 7, 2017. Retrieved March 6, 2017.
  33. "Requesting Permissions at Run Time". Android Developers. Retrieved March 6, 2017.
  34. Hoffman, Chris (October 11, 2015). "How to Manage App Permissions on Android 6.0". How-To Geek. Retrieved March 6, 2017.
  35. Wagoner, Ara (November 1, 2015). "How to take advantage of the new App Permissions in Marshmallow". Android Central. Mobile Nations. Retrieved March 6, 2017.
  36. "Optimizing for Doze and App Standby". Android developers portal. Retrieved November 17, 2015. Google Play policies prohibit apps from requesting direct exemption from Power Management features in Android 6.0+ (Doze and App Standby) unless the core function of the app is adversely affected.
  37. "Tasker has been pulled from the Play Store". Android Authority. Retrieved November 17, 2015.
  38. "Google makes full-disk encryption and secure boot mandatory for some Android 6.0 devices". IT World. IDG. October 20, 2015. Retrieved October 20, 2015.
  39. "Balky carriers and slow OEMs step aside: Google is defragging Android". Ars Technica. September 2, 2013. Retrieved September 3, 2013.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.