6 ms·
What's really terrible here is that Google are saying they won't fix this until their regularly scheduled January release. SERIOUSLY..... They won't rush a fix
by awill 5y ago
What's really terrible here is that Google are saying they won't fix this until their regularly scheduled January release.
SERIOUSLY..... They won't rush a fix out for this? Not even for this??? Unbelievable.
- raverbashing 5y agoIsn't the workaround to uninstall Teams?
- Arnt 5y agoNo, to uninstall and reinstall.
- awill 5y agoI suspect millions of Android/Teams users will never hear of this bug. They won't realize there's action they could take.
- laumars 5y agoAnd what if there is another app that causes the same bug? Teams doesn’t have any special permissions so one has to assume there are more apps out there that could be a problem.
- gotbeans 5y ago> teams doesn't have any special permissions Is that really true though? Scrolling through the permission list on teams, there's a whole bunch I don't usually expect on most apps, ie. "Route calls through the system" (id imagine this is the one needed to implement voip service on top of android). And it gets even worse for apps that can create corporate profiles so they can be administratively controlled remotely by the corp. That's next level of permission bs one has to give up to.
- laumars 5y agoI do get your point that they’re uncommon requirements but my point was Teams doesn’t any uniquely granted permissions that Google have backdoored for Microsoft. So it is entirely possible that another app / VoIP client (or even malicious actor) could prevent emergency calls.
- rekoil 5y agoThis is what I am reading also. Couple that with another similar and recent bug discussed in the reddit thread this links to (https://www.androidpolice.com/notifications-feeling-sluggish-this-popular-android-game-may-be-to-blame/ https://www.androidpolice.com/notifications-feeling-sluggish...) and I'm starting to wonder if there isn't a whole host of unnoticed side effects in peoples Android devices. These are failures on the Android level, apps users can download from the store shouldn't have the capability to break things like calling emergency services, or notifications for other apps.
- mavhc 5y agoAnd that's not a standard permission, have to go to All Permissions to see it, and I don't see a way to remove that permission, or find all apps that have it
- Dah00n 5y agoThen Google should ban the app from play store and auto-delete it from phones until MS fixes it.
- jaywalk 5y agoBecause of a bug in Android? Great suggestion.
- AceyMan 5y agotrying to avoid the trap you speak of: I've submitted a case to my corporate technology department with the permalink to Google's Reddit reply partly so the enterprise can't say they knew nothing about this defect (and I cc: my manager).
- tut-urut-utut 5y agoIf that's the only solution/workaround, I guess Teams should be banned from Play Store and existing Teams app automatically disabled or uninstalled next time a user pings Play Store. In any case, it's Google that is responsible to fix the mess caused by broken sandboxing of their OS.
- PretzelPirate 5y agoI’d now be worried that 911 won’t work with other dialers either. Calls to 911 should probably always be handled by some first-party dialer since it’s not reasonable for everyone to test if their specific installation will be able to call 911.
- jeffdubin 5y agoNote that Google is no longer providing updates (/maybe/ one more in 22Q1) for the OP's Pixel 3, a 3yo device which is otherwise still a great phone. It's simply not good enough. Google needs to support their own phone past three years and be the example to others that ship Android devices. How long are we going to ignore it and let those who can't afford a new phone every couple of years be left exposed?
- ikt 5y agoLooks like it's only impacting phones from 2019 onwards and in very specific circumstances (still not great at all but a very specific bug): If you are unsure what Android version you are on, confirm you are running Android 10 or above by following the steps here. If you are not running Android 10 or above, you are not impacted by this issue. You are also not impacted if you have teams installed and are signed in: If you have the Microsoft Teams app downloaded, check to see if you are signed in. If you have been signed in, you are not impacted by this issue, and we suggest you remain signed in until you’ve received the Microsoft Teams app update. If you have the Microsoft Teams app downloaded, but are not signed in, uninstall and reinstall the app. While this will address the problem in the interim, a Microsoft Teams app update is still required to fully resolve the issue. We advise users to keep an eye out for an update to the Microsoft Teams app, and ensure it is applied as soon as available. We will update this post once the new version of Microsoft Teams is available to 100% of users. https://www.reddit.com/r/GooglePixel/comments/r4xz1f/pixel_prevented_me_from_calling_911/hnrvsr1/?context=3&utm%25255C_source=share&utm%25255C_medium=web2x https://www.reddit.com/r/GooglePixel/comments/r4xz1f/pixel_p...
- maest 5y agoMaybe I'm missing something, but it doesn't sound like it's _that_ specific. From the instructions, the conditions for the bug are: 1. Running Android 10 or higher 2. Has MS Teams installed 3. User is logged out of MS Teams 4. User hasn't reinstalled MS Teams _in a while_ (or perhaps they installed MS Teams in a particular time window in the past) 1-3 seem like fairly weak filters. Unless 4 is a particularly strong filter, this sounds like it would affect a bunch of people.