What’s the difference between AI in mobile phones and regular smart features?
I’ve been hearing a lot about AI in mobile phones lately, and I’m kind of confused about how it’s different from the usual smart features that Android phones already have. Like, I know Android has stuff like Google Assistant, face unlock, and all those smart options, but then there’s this “AI” term being thrown around everywhere. What’s the actual difference? Is it just a fancy name for features we’ve been using, or does it really add something new? I’m not super tech-savvy, so if you guys could explain it in simple terms or share your thoughts, that’d be great. Maybe even some examples of AI in phones?
Best Practices for Managing BYOD in a Mixed Environment
Hello I am looking for advice on managing a Bring Your Own Device (BYOD) policy in an organization with both Android Enterprise & other platforms. What are the best practices for securing corporate data on personal Android devices while ensuring a seamless user experience?🤔 Are there specific configurations / tools within Android Enterprise that you would recommend?🤔 I have checked https://www.androidenterprise.community/t5/tips-guides/bg-p/Resources-msbi guide for reference but still need advice . Additionally; how can we handle compatibility challenges with non-Android devices in this setup? Thank you ! 🙂Securing third party keyboard traffic
We are facing a situation where users are complaining about the default Samsung Keyboard that comes with Galaxy devices as the corporate device. We are looking into providing other options such as Gboard and Swiftkey but the problem is we are unable to fully secure traffic going to these third party services. For Gboard there are some options onthe MDM as amanaged app while Swiftkey does not have many options. Main reason we stick with Samsung is the Knox service plugin which helps secure the device more including keyboard however it only applies to samsung keyboard. With each other keyboard we introduce we have to rely on the key value pairs that come with the app to select options we can lock down as needed. Not all the app developers are enterprise focused so its hard to get any feature requests thoguh. Only other thing I can think of is blocking traffic at a network level to ensure nothing goes through but then we would need to know the addresses that are used. Has anyone faced this situation?
Policy update not removing the google apps like Chrome and Gmail
When utilizing Android Enterprise to administer our collection of Android devices, we've encountered an issue. Specifically, when we apply a new policy to a device and the previous policy included certain Google apps (specifically Chrome and Gmail) and non-Google apps as 'FORCE_INSTALLED,' but the new policy doesn't contain any app, we observe that all non-Google apps are uninstalled from the device, while Google apps(Chrome and Gmail) remain unaffected. Chrome and Gmail continue to be installed in the work profile but are not present in the managed Play Store of the device. Could this behavior be considered a bug, or might there be some aspect we're overlooking in this scenario?
blokking apps on private section using COPE profile with Intune
We have a use case where we use Android devices that are corporate-owned but also personally-enabled. Within our ogranisation, we want the capability to trace and block apps. However, this is currently not possible because the apps are installed in the private section. Is there a way to achieve this in the private section? We are using Microsoft Intune as our MDM (Mobile Device Management) environment.location permission per app
we have an app that requires to set 'Allow all the time' for location permission. We are using Intune MDM and the android 13 enrolled device are using the enrolment of android enterprise corporate-owned fully managed and corporate-owned with work profile. In Intune, there is app config and I set both location auto grant and deploy to the devices. After the app config is deployed successfully to the device, I checked the location permission for the app is still 'don't allow' Then I launch the app to accept the location permission prompt to select 'allow only while using the app'. However, the user is still able to change location permission for the app. Question is this by design that user is able to change the location permission of an app even it is set as auto grant in MDM? Is there a way or is it by design that google does not allow MDM to set 'allow all the time' for an app location permission and it needs to be set by user manually? Could not find any official answer from google or microsoft on this location privacy thing if it is by design.