Restoring Data on a Fully Managed (Device Owner) Android Device During Enrollment
Hello everyone, I’m testing the setup (enrollment) of a Device Owner / Fully Managed Android device, and I’ve run into a question about restoring data. When setting up a personal Android device, you typically get the option to sign in with a Google account and restore apps/data from a backup. However, when I try this on my test device with the fully managed (Device Owner) enrollment flow, it goes straight into the MDM provisioning process. I don’t see the Google sign-in page or any option to restore data from my Google backup. My questions: Is this the expected behaviour for Device Owner (fully managed) setups? Are there any official guides or best practices for restoring user data in this scenario (if supported)? Thanks in advance for any guidance or documentation links!Share your deployment experiences with Android zero-touch enrollment
Hey everyone, In ‘5 Overlooked Benefits of Android Enterprise’, we touched on Android zero-touch enrollment, and it’s something many of you are actively using to streamline your device rollouts. For those in IT, Android zero-touch can be a powerful tool - see our handy guide to learn more. It’s about getting devices to your users ready to go, automatically enrolling in your EMM and pulling down all the right policies as soon as they connect. That means less hands-on time for your team and a smoother experience for end-users. We know real-world deployments always have their nuances, but it would be great to hear about your deployment experiences using zero-touch enrollment: Did you overcome any unexpected hurdles? What was the scale of your deployment - a few devices for new joiners, or hundreds for a company-wide refresh? If you could share one key tip or best practice for someone looking to nail their next zero-touch deployment, what would it be? We’re all here to learn from each other’s stories, and your insights are super valuable. I’m looking forward to reading your stories! Chat soon, EmilieWhat security threats do you experience the most?
Hey everyone, Stop what you’re doing - episode 2 of The Secure Element is out now! Tune in as Bigdogburr and Theresa Lanowitz, Chief Cybersecurity Evangelist at LevelBlue, dive into achieving cyber resilience in an era of boundaryless computing. Their discussion truly reinforced for me just how vital a holistic approach to securing all end-user computing is - from laptops to mobiles, and everything in between - especially with cyberattacks becoming so sophisticated. The role AI plays in crafting these increasingly targeted attacks was a real eye-opener! This episode got me thinking about the real-world threats we’re all facing. What are the kinds of cyber threats you are most confronted with? Cast your vote in the comment section below: Phishing / Quishing/ Smishing (Email, SMS, or QR code tricks) Deepfakes (Convincing fake video/ voice calls) Malicious apps (Apps designed to steal data/ compromise devices) Network attacks (Rogue or Spoofed Wi-Fi, man in the middle, etc.) Other (please share more details in the comments!) And share some wisdom! Do you have some tips on how to identify a cyber attack? If you’ve been targeted, what’s one key lesson learned that you think everyone should hear? Looking forward to reading your stories. Chat soon, EmilieWhat OS rel. your Android fleet is running ?
I'm just curious to know how other corporates doing OS patching. We at SAP only allow 2 latest OS versions which means today we only support Android 14/13. Our Android fleet is approx. 10 000 devices. Mixed Samsung and Google Pixel, no other manufacturers allowed. 70% of our Pixel devices running already Android 14 11% of our Samsung devices running already Android 14 How about yours?Share your AI Success Story: Android Enterprise customer testimonials & quotes needed!
Hey everyone, I hope you are having a good week. AI is evolving fast, and we're curious how it's starting to shape your work on Android. Has your company embraced it wholeheartedly or are you finding people more reserved when implementing AI? As part of our end of year festival, we had a brilliant community post by BenMcc all about the hopes and pitfalls of AI so far (well worth the read if you haven’t already), and we’re keen to keep the conversation going - what do you think of his observations about ownership/accountability and the future of AI? Whether you're a seasoned AI user or just dipping your toes in, we'd love to hear your experiences—even if they're initial observations or pilot projects. We’re looking for real-world examples and specific, impactful quotes that can be featured across our channels (or we could just have a great conversation below! 😀). It would be particularly interesting in learn about: Specific AI Use Cases: How are you leveraging AI tools in your daily work on Android? Google AI Tools: Are you using Gemini for Google Workspace, Circle to Search, Gemini models, on-device AI tools on Pixel, or other AI tools? Organizational Impact: How has AI improved your productivity, reduced costs, or streamlined processes? For example: "Gemini for Google Workspace has saved our team [X] hours per week by automating [specific task]." "Circle to Search has improved our ability to [specific action] while on the field." "On-device AI on Pixel allows us to [specific task] without needing constant internet access." Thank you in advance, Lizzie (and the Android Enterprise Team)
Supporting every employee: Discover 9 helpful Android accessibility features
In today's workplace, making work devices accessible is not just good practice, it's essential. Almost half (45%) of employees with disabilities find the accessibility features of their workplace software barely adequate.1 The reality is that inaccessible workplace software creates a significant challenge for many employees, underscoring the gap in providing truly inclusive tools. Our new Android Enterprise blog post, "9 Android features to support workplace accessibility", explores how Android is addressing the need for better assistive technology with a robust suite of built-in vision, audio, and mobility accessibility tools—designed by and for people with disabilities. It covers key topics like: Supporting a range of visual needs with Android's adaptable vision features: From Braille Display support and the AI-powered Lookout app to TalkBack screen reader, Android offers a range of customizable visual tools. Helping teams amplify what matters at work with Android's hearing tools: Android provides audio features that adapt to a range of hearing needs, including Real-time text (RTT), Sound Amplifier, and seamless hearing aid integration (including the new LE audio support). Unlocking personalized control for employees with motor limitations: Support employees by providing tools that help them own their workday with personalized control such as, Gesture Navigation, Camera Switches, and Action Blocks. This isn't just about meeting accessibility standards – it's about helping teams interact with their work devices more effectively and independently. Read the full blog post here to learn more. Now, let's open up the conversation! We want to hear from you. What accessibility challenges are you facing in your organization? Do you use any of the features mentioned? How can we, as a community, advocate for better accessibility in the workplace? Are there any other features you’d like to see in the future? Share your thoughts and experiences below! 1 https://www.capterra.com/resources/technology-accessibility/
[Day 4] Community festival : Introduction to a mobile only strategy in a large company
Hello all, We are pleased to share with you some insights and achievements of our mobile only strategy. But first, I am really not sure sure you have heard about Thales ! Thales’s mission is to empower customers to face their decisive moments with confidence. Some key figures and core business below : What is our main idea ? Android devices are enough mature to start creating a working environment in Mobile Only strategy which means replacing PCs when they are not relevant. Which leads to: - Increased end users productivity - Reduced business and IT costs - Reduced carbon footprint - Better attractiveness and digital modernity for end users What we have achieved since 2021? The 1st step of this long journey - An agile project method focusing on the end user, really - A configuration designed, built and maintained WITH security officers from day 1. - An end-to-end solution imagined for the last step. - A 1st macro use case frontline workers, focus on logistics and production Just have a look on this video released in 2022, showing our fisrt production line in with our new digital workplace ! I hope you liked it! 2 years ago already… What are our next steps ? - An extension to other use cases. - A pedagogy for the entire "Android OS" ecosystem: Employees, vendors, customers to foster activities & new stuff - The pleasure of exchanging with you all. Vincent Turquet Yann Roland[Day 5] Community festival: Looking ahead - What could be next for Android?
Next year will mark 20 years since Google’s acquisition of Android Inc., arguably one of the most transformative decisions of the modern era for the development of mobile and enterprise mobility. Without Android, not only would none of us be here to read this week’s Community Festival content (it’s been fantastic!), but the mobile landscape and pace of innovation could have been vastly different (where would Apple get their features!? 😉). It goes without saying the careers of many of us would likely have taken completely different paths, as well. I’d still probably be doing disaster recovery 🙃 Android has changed a lot over the last 20 years. What was originally an OS created for cameras before launching on phones with physical keyboards and trackballs, such as my first Android phone here, the HTC Dream, has grown immeasurably to get to where we are today. Some of today’s workforce may not even remember Device Administrator management, nevermind the Holo phase Google went through over a decade ago (it was actually brilliant, I miss Honeycomb & the Xoom, my first ever Android tablet). The Holo UX, as pictured here (source: Wikipedia), serves as an excellent reminder of just where we’ve come from and how the platform has grown. Obviously today we’re in the world of Material Design, but it’s not just the UX that’s changed, we’ve had entire derivatives of Android for various use cases - WearOS (Originally Android Wear), Android TV, Android Automotive, Android Things (RIP), Android Enterprise (of course), and many significant projects in between. But this all begs the question: What’s next? If you’ve been perusing the news lately, you'll have no doubt noticed we may be in for exciting times ahead. Join me as I explore what we could be seeing in the coming years for Android, and its implications for enterprise. Do keep in mind it’s speculative, unless the PMs lurking around fancy chiming in with their own commentary down below 😉 Android & ChromeOS merge The prospect of Android and Chrome merging isn't new, in fact it is already underway. As of June, Google announced intentions to integrate with “large portions of the Android stack” - presumably to make better use of resources & engineering efforts. Prior to that, Google was experimenting with ChromeOS virtual machines running atop Android’s Virtualisation Framework (AVF), raising hopes that would become the Android desktop mode we all desire (spoiler: nope). Recently though more and more reports are popping up from outlets suggesting ChromeOS will fully migrate to Android in future. While it’s not a given, some additional indicators, such as the terminal app popping up in Pixel’s ongoing QPR beta, and likely Linux support in AVF effectively matching what ChromeOS offers today with its own terminal and Crostini (Linux on Chromebook), could allow ChromeOS to ditch its own implementations and focus on the desktop experience while Android does the heavy lifting elsewhere. What could this mean? ChromeOS and Android have an interesting relationship, and in my experience there’s a well-defined line in the sand for enterprise use cases where Android excels, and where ChromeOS is recommended instead. I’ve come up against this occasionally when advocating for Android TV management, equivalent to Apple’s tvOS (and maintain this is still a low-hanging fruit!) for digital signage applications and in hospitality settings. They both have their own approaches to enterprise management, the latter with a separate licensing model on top of what customers would pay an EMM vendor to manage ChromeOS devices, something I’d hope would go away if ChromeOS does fully adopt Android’s underpinnings. We could end up seeing some of the enterprise APIs finding their way into Android, as well as new management controls around when desktop mode could be used, what Chrome Web Store apps are available - if the store is available at all. Silent deployment of plugins and store apps.. all from a standard Android policy. It would be magnificent. More broadly, it could mean seeing Android tablets, laptops, desktops, and even full convergence with a hybrid Android launcher-to-ChromeOS desktop experience depending on the form factor or the display(s) a device plugs into. Convergence is a topic I’ve been interested in for a long time, so I’m aware desktop mode in Android has been lurking in the background since Android 10 without a considerable change over the years since - at least in AOSP - OEMs like Samsung, Lenovo/Moto, and others have been pretty successful in filling the void - not enough to fully convince me to entirely switch out my Mac & Linux devices, but they function great as a secondary option. If ChromeOS comes over to Android and the prospect of convergence becomes reality, it would be fascinating to see what becomes of solutions like DeX, or how they’d adapt, at least, but more importantly, it could usher in a reality where this really could be viable, even for the holdouts like me dependent on desktop applications. Linux & virtualisation support Even if we weren’t to see a future where ChromeOS and Android entirely merge, Google’s recent work with AVF in Android 15, which as above has seen builds of ChromeOS and Linux running, is exciting. One of the bigger limitations I have with using Android for everything is a reliance on Linux applications - desktop Chrome for plugin support, Android Studio, VSCode.. Even native graphics applications like GIMP or Inkscape. There are gaps today that only desktop apps can fill for me. Android has its alternatives - some pretty good - many not good enough, and the prospect of running desktop applications through Android would be a game-changer. For organisations though, wouldn’t this be a risk? Managed devices spinning up builds of Linux to run unapproved applications? Imagine the furore. Clearly this requires some enterprise control; I’d be surprised to see more than a simple toggle for allowing or disallowing Linux support in the beginning, which could be as simplistic as hiding the terminal app. That’s boring though, right? It would be so much more interesting to be able to remotely configure the Linux image, hook the build into an organisation’s RMM/UEM platform (or support cross-platform commands to save a license fee on platforms that’ll charge once for Android, and again for managing Linux). I’m getting ahead of myself, of course, and I’m sure there are so many applications for virtualisation that not only have I omitted here, but probably haven’t even considered being someone who doesn't manage these environments on a daily basis. It’s exciting nonetheless. Android for XR So a little bit about Play Protect (GMS) certification first. The reason we don’t see certified wearables running the same Android you see on your phones and tablets out in the wild today is due to the very strict constraints Google enforces in order to certify an Android device to run Google’s apps and services. If desired, you can read more about this here, but to summarise: Devices must adhere to hardware requirements and support Android in a way that is compatible with the ecosystem, and the XR segment just.. doesn’t. Applying rules and requirements of a phone/tablet user experience to non-standard form factors doesn’t work. I’ve helped a few companies over the years trying to work towards getting their devices running certified Android and it has been a lost cause - could you have a pair of smart glasses projecting the Android home screen with a particular app layout as the primary UI? Sure. Would it be a terrible user experience? Entirely. Almost every OEM building these devices has purpose-built, tightly integrated user experiences that look nothing like an Android phone for obvious reasons. Oh, but what about Android TV? Those boxes don’t have a display. WearOS screens are typically tiny and don’t show the Android home screen? Your friend’s Volvo has the Play Store but that’s not a portable device connected to a battery (we’ll overlook it being a car). These devices have their own certification categories with their own requirements, and these can all be seen with Android’s CDD, or Compatibility Definition Document. This is the public aspect of certification, the rest is hidden in partner docs. Because there hasn’t been a category for XR, devices default back to phone/tablet, and that becomes the blocker. But that could change. With Samsung reportedly edging closer to debuting their XR headset, it’s not a stretch to imagine these may provide access to Google services. It’s certainly not guaranteed, after all Google Glass was a thing and that never obtained certification. Times have changed, however, and Samsung being a very persuasive partner in the ecosystem will have high chances of bending Google’s ear to supporting such a form factor with all the benefits of Play Protect certification. Obviously just throwing Google apps and services on an XR device won’t be enough, and the appropriate work will be required to make them function well, but this then opens the door to a whole new category of certified devices, and would satisfy a common(!!) request I see almost monthly to allow global, seamless and consistent enterprise support for this category of device. To be fair, Samsung will likely handle this with Knox APIs directly as well, but that doesn’t help the rest of the ecosystem. Again, no guarantees, after all Android TV and WearOS have been around for a long time without official enterprise support; the APIs are there for the most part, they’re just not easy to enrol. But wouldn’t that be great? It would be a natural expansion from all the wonderful work Google have done in large screen and non-standard form factor improvements in recent times, too. What’s next for you? That’s my ramble over! How about you? What are you optimistic about seeing in the next few years for Android - in or out of enterprise?[Day 2] Community festival: The long road from SMS to RCS
Hello everyone! In late summer, I went on vacation to the USA and visited a few theme parks. To prepare for my vacation, I read up on the rules of etiquette in the USA so that I wouldn't stand out as a tourist and wouldn't put my foot in my mouth. As a European, I was totally surprised by one topic because I had never heard of it before: "Green Bubble vs. Blue Bubble" While SMS plays at most a role in two-factor authentication in my environment, it is still widely used worldwide. A little bit of history from the last 30 years The first concept for SMS (Short Message Service) was drafted in 1985. This concept already had a limit of 160 characters per message. It was assumed that people would not usually use more characters in a fax or postcard, which meant that the 160 characters were completely sufficient for the service. After the first SMS with “Merry Christmas” from Neil Papworth to Vodafone manager Richard Jarvis on December 3, 1992, SMS was commercially launched in Germany at CeBIT 1994. SMS was incredibly popular back then and peaked in Germany in 2012 with 59 billion short messages. In 2023, “only” 5.3 billion text messages were sent. But texting was not that cheap. The price per message was usually 19 cents. Initially a little higher, but later the price dropped to as low as 6 cents with low-cost providers. From 2002, it was also possible to send media such as pictures and videos via MMS (Multimedia Messaging Service). Unfortunately, the service was rather expensive at around 39 cents per message and also limited to just 300KB. Videos via MMS were pretty much a pixel mush. Vodafone buried the MMS service in Germany in January 2023. SMS flat rates were not worthwhile and uncommon back then because they were too expensive. As smartphones became more and more popular on the market, people switched from SMS to messaging apps with more features. WhatsApp has become the standard for messaging. The advantages did not have to be explained to any age group for long: With an existing internet connection, you can write an unlimited number of messages. Photos and videos can also be shared easily. You also see a read receipt and an online status. There is a very large selection of messaging apps. WhatsApp, Signal, Threema, Viber, Telegram and many more. The only problem is convincing other people to use a better or more secure messenger. If something simply works and people are satisfied, it is very difficult to argue against “never touch a running system”. Green vs. Blue Bubbles Apple has introduced iMessage in iOS5. iMessage replaces SMS and MMS with a new messaging service, provided that both users are using an iOS device. Messages are encrypted end-to-end and the standard messaging app also enables more features. Sharing photos and videos, read receipts, stickers, other attachments, group chats and much more. iMessage messages are displayed with blue bubbles and SMS/MMS messages are displayed with green bubbles. In the USA, SMS flat rates seem to be offered in most plans. In 2011, there was a peak of 2.3 trillion SMS/MMS. Unlike in Germany, SMS remained at a similar level and 2 trillion SMS/MMS were still sent in the USA in 2021. In addition to flat rates, user behavior could play a role. Many people seem to use the standard apps on devices. The iPhone is also very popular in the USA and has an extremely high market share of around 59%. This share is only around 28.3% worldwide. The Green vs. Blue Bubble topic has taken on a social dynamic all of its own. When exchanging phone numbers while dating, some dates are ghosted as soon as a green bubble appears. Android users are excluded or even bullied at school, for example, because the green bubbles would break the group chats and functions would be lost. In my opinion, we should be connecting people in the communication industry, not building walls or maintaining them. Unfortunately, in 2022 it didn't look like Apple wanted to improve communication between iOS and Android. [Link] If only someone would push modern standards so that everyone could communicate better and more securely. https://www.android.com/get-the-message/ RCS (Rich Communication Services) has been under development since 2007. RCS is a IP-based protocol standard for short messages that will ideally replace SMS and MMS in the future. The standard is defined by the GSMA (GSM Association). Google acquired Jibe Mobile in 2015 and has been working with GSMA on the “Universal Profile” standard for RCS ever since. Attempts were already being made to establish RCS as a standard around 2013. Some carriers had agreed on an RCS standard and launched RCS-e / “joyn”. However, the RCS solution with the joyn app failed to establish itself and was abandoned. With Google Messages, there is a widespread standard messaging app on Android devices that supports RCS. If the other person does not use the preferred messaging app like WhatsApp, there is ideally no fallback to SMS. Instead, you have a solution with RCS with typing indicator, read receipts, high resolution picture/video sharing, voice messages and reactions. And if all participants use Google Messages, all data is encrypted end-to-end. RCS also offers business messaging (B2C). Companies can verify their identity and send customers better and more complex messages than with SMS. For example, tickets for trains, planes or cinemas can be sent directly as a QR code as an RCS message. Or make contact with customers interactive via chatbot. Google, for example, prefers to use an RCS chat for Google verification codes. What does it look like? If the other person does not have RCS, SMS/MMS is used As soon as RCS is available or no longer possible, this will be displayed + Typing Indicator and Emoji Reaction You can check whether the messages are encrypted in the message details A wide range of files is supported. You can also add an emoji theme to voice messages in Messages. On some devices, automatic audio transcription is also possible so that you can read the voice messages. Setting up RCS The RCS settings can be checked in the Google Messages settings The carrier plays a role in RCS registration. In this case, RCS was blocked by the carrier for this subscriber. As a result, it was not possible to set it up. However, this should not occur with private SIM cards. In this case, RCS is active Finally! This year, Apple finally introduced the RCS Universal Profile 2.4 in its Messages app with iOS 18. I think it's great that Google has pushed the topic of RCS forward. I also think it's honorable that Apple has implemented RCS. I hope that they will also continuously implement newer standards of the Universal Profile. Samsung can also be cheered, as they have also implemented RCS in their products for many years. It's about time we moved on from a telecommunication standard from over 30 years ago, where people were thinking of faxes and postcards for the length per message. It is truly no easy task to create a bridge between the iconic SMS and modern messaging services with RCS. However, the current progress makes me feel positive. RCS still seems to be at the beginning, but 2024 was a very positive year for the spread of RCS. 🎉 In over 30 years of SMS, there has been a lot to experience. Do you have any stories about SMS? Back then, I had a deal with the carrier with my PrePaid plan. For every ~30 (I'm not sure of the exact amount) SMS I received, I received credit worth one SMS On New Year's Eve, massive amounts of New Year's wishes were sent by SMS in Germany. It was like an annual DDoS attack on the carriers. The messages often arrived at the recipients several hours later.
