312
Microsoft Authenticator might exclude GrapheneOS in the future due to root detection
(piunikaweb.com)
this post was submitted on 06 Mar 2026
312 points (97.6% liked)
Android
21559 readers
748 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not all works would allow it, but why not Graphene on work phones.
What happens if the worker doesn't have a smartphone, or has one, it breaks and they don't have money to buy another for while, or what if they install a random app that encrypts their mailbox?
Even if you live in a 3rd world country where employers can force it, it's a stupid decision for the business.
I don't understand your line of questioning. If a bad thing happens then a bad thing happens. Potential for bad things indeed makes companies likely to lock down devices if they provide them, hence the qualifier "not all works would allow it." From an employee perspective, if you have the freedom to do it then more secure OS is more secure.
I have a work phone.
If didn't have a personal phone, it wouldn't matter.
If it breaks, they have insurance to replace it immediately.
There's no risk it will stop working because I didn't pay the bill.
And I can't install random crap because it's locked down.
And they have options like remotely wipe the device, if they think something weird is happening.
From my side. The phone is turned off the microsecond I clock out.
I can tell you what we do. Here's your yubikey. Then most find a new phone after a couple weeks.