this post was submitted on 06 Mar 2026
298 points (97.8% liked)

Android

21559 readers
710 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

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 2 years ago
MODERATORS
top 50 comments
sorted by: hot top controversial new old
[–] picnic@lemmy.world 2 points 1 hour ago

Now this is shitty. Our company allows only authentication with the app, and I was really happy to give up the shitty phone they offered and just carry one.

I saw the news earlier this or last week, but as my grapheneos is not rooted, didnt think much of it.

Fuck em. I just got grapheneOS and I advised my workplace we will need a workaround for authenticator.

[–] GreenKnight23@lemmy.world 7 points 10 hours ago

I mean...okay?

I have a work phone for this exact reason.

work phone stays on my desk. I have removed the microphones. I turn it on at the start of every day, and turn it off at the end of every day.

good luck with that plan Microslop. looks like Microslop is trending too!

1000003153

[–] Reygle@lemmy.world 15 points 12 hours ago* (last edited 12 hours ago)

Oh no

Anyway

Microslop authenticator might not work for my zero Microslop accounts, lack of Microslop sloperating system, OR their piece of shit cloud platform that I refuse to touch?

WHAT WILL I DO

[–] arcine@jlai.lu 20 points 16 hours ago (2 children)

That doesn't make sense to me, afaiu :

GrapheneOS is NOT rooted by default, and they explicit recommend NOT to do it, because it invalidates a huge part of their privacy guarantees.

[–] cmhe@lemmy.world 1 points 2 hours ago

privacy guarantees

security guarantees, not privacy guarantees.

With root you can actually control what kind of things each app does and stores, and check what data it transmits to remote servers. But it also breaks/weakens the android security model, where apps can do, store or transmit stuff protected from the eyes of the user of the phone.

[–] Honytawk@feddit.nl 10 points 14 hours ago (1 children)

Yeah, and Microsoft policy is just about rooted phones.

There isn't any reason to mention GrapheneOS, unless it is to generate unwarranted outrage.

Which seems to be working on a lot of folk on here.

[–] AndrewZabar@lemmy.world 4 points 12 hours ago

Well it could just be part of the collective corporate alliance that will always do anything they can to make any kind of freedom cost more for everyone. GrapheneOS is taking your freedom and not feeding on the corporate-issued fodder, and well, they don’t like that. So this is just one more small difficulty added to that choice.

This kind of thing is only the beginning. It won’t be long before absolutely nothing will work on any freedom-oriented OS, software, hardware etc.

Some fires need to start, and soon.

[–] kyub@discuss.tchncs.de 53 points 19 hours ago* (last edited 6 hours ago) (5 children)

Use Aegis.

The MS Authenticator contains analytics & telemetry & way too many permissions and should not be used: https://reports.exodus-privacy.eu.org/en/reports/com.azure.authenticator/latest/ (it looks more like a scam than legitimate, but that's exactly what Microslop is in 2026...)

For comparison, Aegis is a legitimate app that only does what it should do: https://reports.exodus-privacy.eu.org/en/reports/com.beemdevelopment.aegis/latest/#permissions

Any other authenticator also works with any MS service so there's no reason at all to use the MS Authenticator unless you like handing over more data to MS for no reason. EDIT: According to comments, your company might have the option to enforce usage of MS Authenticator only. But this doesn't seem to be the default, at least in Germany where I've heard from 2 sources that they can use any authenticator app for M365 for example.

By the way, Graphene OS is NOT rooted, but what does truth or sane app behavior even mean anymore for Microslop in 2026... Just stop using that garbage.

[–] fluckx@lemmy.world 5 points 16 hours ago (2 children)

Agree for personal use.

Professionally I've had situations where Ms authenticator was the only option because the only 2FA they allow is push notifications on the authenticator app. :(

I even used freeotp+ for my ORG 2FA and aegis for my personal so I could easily keep them split ( and you can export / securely store the backups somewhere ).

Time to get corps to ditch Microsoft >.>

[–] lka1988@lemmy.dbzer0.com 6 points 14 hours ago (1 children)

Professionally I’ve had situations where Ms authenticator was the only option because the only 2FA they allow is push notifications on the authenticator app.

If a company requires me to install specific apps that may or may not work on my device, I expect that company to provide me with a device that can be set up for their stuff.

I've run two separate phones for nearly 15 years now: my personal phone, and a work-issued phone. The work phone is turned off and left on my night stand as soon as I get home, and only turned on again when I'm getting ready to go back to work. I don't carry it 24/7 as some have been led to believe, for some reason. It's really nice to have that separation. And work pays for it.

[–] definitemaybe@lemmy.ca 1 points 1 hour ago

Peach. Separation is where it's at, and companies should be required to provide technology required for work.

In an ideal world "No, I don't want that on my personal device" should be sufficient, but it's a lot harder to argue with "No, I literally cannot install that on my device; it's incompatible. Provide an alternative for me."

I'm finally taking steps to walk the walk re: phone separationβ€”I'm hoping the Click Communicator pans out, since it seems like the ideal work phone. (I get a stipend for tech, so I can get whatever I want. I've been pocketing the extra cash, but it's time to get an actual work phone.) I'm just hoping I can wait it out and ignore the Authenticator warnings until then, or maybe look into Magisk Hide or whatever.

[–] besbin@lemmy.ml 4 points 15 hours ago

We do need to get corps to move away from closed source protocols like MS, Google, Meta and others push notifications though. Those are not in anyway safer and are just basically trap to force people to use their apps

load more comments (4 replies)
[–] shaggyb@lemmy.world 51 points 23 hours ago (4 children)

That's fine.

Any job that wants you to use certain software can provide a device it'll run on for you.

[–] cerebralhawks@lemmy.dbzer0.com 10 points 22 hours ago

Amen to that. Even if your computers will run it, provide the device. I'm not installing shit on my home computers.

My job has suggested it to me. I say "you know how all these computers run Windows?" They nod. "Mine doesn't. It's a Mac." That usually shuts them up. Never mind that most of what we run will, in fact, run on a Mac, and there's very little a shitty Wintel box mass produced for the enterprise can do that my Mac can't do. I mean, I can run Deus Ex natively on the work computer, if I wanna catch hell for it. (But it would be fucking hilarious, especially if I'm at the part where JC Denton hands in his "resignation.")

[–] VitoRobles@lemmy.today 2 points 15 hours ago

Yep! You want me to use your microslop on your hardware at your company, fine.

A company that has you use your personal device is an awful company and huge red flags in terms of privacy.

load more comments (2 replies)
[–] gravitas@pie.gravitywell.xyz 19 points 21 hours ago (2 children)

Interesting considering grapheneOS does not actually support rooting.Β 

[–] buddascrayon@lemmy.world 20 points 20 hours ago* (last edited 20 hours ago) (2 children)

This is the thing that kills me about the corporate anti-GrapheneOS sentiment. It is 100% a more secure phone, and yet every measure they implement against it cites security as a reason. Total and absolute bullshit.

[–] Buddahriffic@lemmy.world 4 points 15 hours ago

Because it isn't really about security. It is about control.

[–] brax@sh.itjust.works 10 points 19 hours ago

I mean, they argue against rooted phones as a security reason, but my rooted phones used to be much more secure than they were when they were stock.

Just more of the same idiots ruining shit for everybody.

[–] Honytawk@feddit.nl 3 points 15 hours ago* (last edited 15 hours ago) (1 children)

Which means the entire article is bullshit.

It literally states that Microsoft changes its policy to not allow rooted devices. So GrapheneOS has nothing to worry. It doesn't affect them. Why does the article mention it then at all?

Seems like a clickbait article

[–] hersh@literature.cafe 2 points 10 hours ago

Which means the entire article is bullshit.

Not necessarily. It could just be that Microsoft's "root" detection is misnamed or poorly implemented. They would not be alone in either case.

[–] KiwiTB@lemmy.world 91 points 1 day ago (1 children)
[–] Daniel_@discuss.tchncs.de 47 points 1 day ago (27 children)

Unfortunately not for me. I use Graphene and my company uses M$croslop.

[–] ViatorOmnium@piefed.social 89 points 1 day ago* (last edited 1 day ago) (23 children)

Work stuff should be on a work phone.

I don't understand why either the worker or the company would ever allow the use of personal devices for work.

load more comments (23 replies)
[–] Fmstrat@lemmy.world 2 points 15 hours ago* (last edited 15 hours ago)

Old phone with remote desktop.

Works like a charm for many of these types of things. You can also forward notifications into NTFY or Matrix.

load more comments (25 replies)
[–] absquatulate@lemmy.world 18 points 1 day ago (8 children)

This is what I fear will happen to GOS on Motos. Google decides to mark them as rooted so buh-bye banking apps and others that require a "secure" os.

[–] skuzz@discuss.tchncs.de 2 points 14 hours ago* (last edited 14 hours ago)

Another banking app thread, fun! Don't use phones for banking. One just trades privacy for perceived convenience. For "safety" you give your bank:

  • Unnecessary lower-level system access than normal apps, for SAFETY!
  • Your location as often as they can harvest it
  • What apps you have installed
  • Any metadata they can exfiltrate through trackers in the app that can be mated with metadata from other app trackers
  • Any personal information they can gather from your phone

Furthermore, if you use tap-to-pay, which some banks require their app be installed to use, you're then giving every transaction you do, with or without tap-to-pay, to the operating system provider and any third parties along the way. Use your credit card at a store and the phone's at home? That transaction still gets scooped up.

Finally, you have this object you always carry with you, that has access to all your financial information, that a bad guy just has to punch you in the face to get you to log into your bank and delete all your money. Bravo! With a card, it can be shut off afterwards, and the bank can mark any transactions happening afterwards as fraudulent. With a phone app, they can Zelle themselves your money and the forward it to some cryptocurrency and good luck. Then clean out your RobinHood, your DraftKings, your CoinBase, your 401k, and anything else they find along the way.

Use the bank webapp if one is desperate.

Banking. On. Phones. Is. Stupid.

[–] Onomatopoeia@lemmy.cafe 15 points 23 hours ago (1 children)

Except they're not rooted - GOS devs don't even approve of root usage

[–] absquatulate@lemmy.world 16 points 23 hours ago (1 children)

It doesn't matter if they are or not. Google can deem them modified or not secure devices and they can do fuck all about it.

[–] e8d79@discuss.tchncs.de 14 points 22 hours ago (1 children)

The difference being that Motorola is a well established device manufacturer and not just a community project with minimal funding. Google using play integrity to exclude a competitor could be very easily seen as an abuse of market power and they already have problems with antitrust laws.

[–] Stez827@sh.itjust.works 2 points 11 hours ago (1 children)

Not with the current trump administration. They can do whatever they want

[–] Turret3857@infosec.pub 2 points 10 hours ago

other countries exist

load more comments (6 replies)
load more comments
view more: next β€Ί