States also regulate 911 service. Try your state's office of emergency services.
There's something called "Kari's Law" that may apply here. This was passed in 2018 after someone was being attacked in a hotel room and their 9 year old daughter tried to call 911. She couldn't get through because the phone system required dialing 9 for an outside line. So, now, all business phone systems are required to recognize and pass through 911 to the main phone network. There are criminal penalties. (Microsoft might argue that "Teams" is not a "multi-line telephone system". That probably wouldn't go far with a jury. The clear intent of the law is that if you interpose something between a phone handset and the 911 network, it has to pass through 911 calls.)
The whole 911 area is heavily regulated, since it requires that so many things interoperate reliably.
> We determined that the issue was being caused by unintended interaction between the Microsoft Teams app and the underlying Android operating system.
As someone whose organizational policy signs my Teams client out after a couple hours of inactivity, I would love to know how on earth this is possible. I truly am at a loss, and I am furious at the thought that I have been unable to dial 911 for who knows how long.
At least I know the ten digit number for my local emergency services, but the average person probably doesn't. This is unacceptable.
They need to release more technical details on this to restore confidence. How can a sandboxed user installed app with limited permissions cause dialing 911 to fail? How do they know other apps won't cause the same issue?
And they mentioned an Android update, but what about the millions of Android phones that aren't getting regular updates? Does that mean there's potentially millions of phones that can't dial 911?
I like Pixel and Android, but am seriously thinking of switching to iphone because I really need a phone I can trust will dial 911 when I need it.
Google wants you to blame Microsoft Teams for this, and judging from some other comments that’s nearly working. But, the blame is entirely on Android. It doesn’t matter how badly Teams screwed up - it should not have the ability to mess up a core system function like this.
Let’s not forget - someone very nearly could have died thanks to this glitch. Thankfully, a landline was available.
> "I am furious at the thought that I have been unable to dial 911 for who knows how long."
Initially I thought the above comment was unreasonable. But when I put myself in the same shoes, I have the EXACT same feeling.
It is like the person who was coming at the intersection at blaring speed, but missed me. The fact that he COULD have hit me, and if that happened, I would likely have died, is a very frustrating thought. But when conveying it to a 3rd party, I feel the 3rd party might think "hey, its ok. nothing happened. you are safe. he did not hit you, so why are you upset?"
This might be related: https://blog.enablingtechcorp.com/planning-emergency-calling...
"Routing emergency calls to the appropriate 911 Public Safety Answering Point (PSAP) is a legal requirement in the United States [...] Teams can determine an Emergency Caller’s current location and automatically pass the call and the current location information to the appropriate PSAP"
Agreed. As a Pixel/Android user who has never used Microsoft Teams this is still incredibly concerning.
A third-party app causing this issue on accident means a third-party app could cause this issue maliciously and any app not part of the base operating system should not be capable of causing an issue interfering with emergency calling.
I assume/hope their January 4th fix addresses whatever the issue is at a more fundamental level, but this seems like the sort of thing that should be addressed a lot sooner than a month out.
Weren't emergency services numbers supposed to be available, not matter whether the phone is locked or not, and does not even require a SIM card?
Then how come an user mode app can block calling numbers that were supposed to be available where is there is cellular coverage?
I can't answer that but I run Teams on Android and it's just a terrible app. Its problems have affected my entire phone before. Like for example when it wouldn't stop blinking and each blink reset whatever I was doing so I had to quickly switch out of it between blinks and then force kill it from Settings.
I only installed the teams app on my phone, because their web app only works in selected invasive browsers on the desktop, but not in Firefox, which I found already infuriating.
Why can't we have open standards for communication in 2021, where everyone can just use the software that they trust? I would never use teams if I had a choice, besides looking for another job.
I also know the number for local emergency, but needing to wait for my phone to reboot during a stroke (and my phone takes a looong time to sounds really scary.
My feeling is that Google is not capable of fixing fundamental problems of Android. Every year they change some colors and rounded edges (it's starting to get hilarious seeing the design of their apps being revamped over and over again), and add features invented by their designers nobody asked for. But the keyboard lag, the storage footprint (why must an ever so slightly older phone with 16GiB internal memory be discarded because His Majesty Android demands almost all of its space for itself?), those will only get worse every release. I think they simply don't care. It's all about futuristic colorful stuff that sells. Android will never be a humble, efficient, reliable platform.
As for this issue. All I can think of is the tragedies it may cause. It's a cliché: software developers are not responsible, except when their PR forces them to take action.
Google has popularized the practice of keeping hordes of UI designers on payroll and changing the UI every single release. It's fucking cancerous. Nothing can ever just stay the same and work. Users have to be in a constant state of headache to relearn shit for the nth time.
Is there any product being developed by a giant company for >10 years that isn't a bloated mess at this point?
I see feature creep and sloppy functionality in the core as a symptom of the usual tech project management style, where there's pressure to make up random metrics to have flashy results over maintaining existing functionality.
Proper testing has the same impact for your performance than just ignoring the metrics you are supposed to test. You can also get praised when you fix the problem your sloppiness caused.
> it's starting to get hilarious seeing the design of their apps being revamped over and over again
I can't stand that anymore. Every single updates make things more and more unusable, they hide settings, they make buttons bigger for no reasons, &c.
They even managed to butcher the alarm app... it looks like an app designed for visually impaired people (which would be fine if it was an option and not the default/only choice).
Android has grown too big for google to maintain, which is why most change seem to be looks and user-goodies, rather than focusing on bug fixes or stability.
I've experienced the severe decline in stability over the last 10 years of use, and on flagship phones, not outdated.
Currently my Pixel sometimes displayes an open app partially off screen, or scaled wrong and clipped --- this is basic UI that worked for years and is now broken again.
"Based on our investigation [...] We determined that the issue was being caused by unintended interaction between the Microsoft Teams app and the underlying Android operating system. [...] 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. [...]"
Now I'm really curious as to what that "unintended interaction" was.
IMO while Microsoft and Google should work together to solve this as soon as possible, the longer term solution should not involve Microsoft. This sounds like something Google should fix at their end.
No customization done by the user, including installation of apps should prevent a user from being able to call 911, period.
I worked at Motorola's cellular division 20 years ago. I recall a "stop ship" incident when a 911 bug was discovered. That is, we halted the factory and shipments until the bug was fixed and a new software image was available.
The phone's callstack takes a lot of special actions when calling 911, including locking onto any tower even if it is not in the preferred roaming list. As with many exceptional conditions, these code paths are often not as well tested.
I wonder if there should be a 911-like test number that would cause the phone and the network to go through the emergency call procedure, just not connect to the actual call center.
"We believe the issue is only present on a small number of devices"
-> Reads like damage limitation. Don't believe it, say why!
"we are currently only aware of one user report"
-> Irrelevant. Damage limitation. Don't ever write this. Most users will never be able to recognise it as an Android problem, even fewer will have the ability to bug report it.
Since I don't use Find My Phone often enough, my Pixel 3 helpfully decided to remove location permissions from it. Would've been in for a surprise the next time I lose my phone had I not caught the notification.
Oh wow, this is true for me as well. Need to check if the app permission is required or if the location tracking works separately through some system service.
If you mean the Find My Device app it only asks for foreground location permission so I would assume the actual device "beacon" is part of the system not that app.
I've lost a phone with location tracking turned off. You can still disable the phone remotely and assign a lock screen message for the findee to contact you.
Problems I had on Android phones at various times in the 10 years I owned them (mostly Nexus / Pixel):
* Can't make calls
* Can't receive calls
* Can't send text messages
* Can't receive text messages
* Receiving text messages out of order or days late
* Can't take pictures
* Can take pictures, but they don't save
* Phone randomly shuts down when cold
* Phone randomly shuts down when hot
As much as I liked Android when it worked well, in the end I realized the bugs in the OS were putting me at risk of physical harm or, at the very least, incredibly damaging data loss or missed communication.
I bought myself a $400 iPhone SE. It may not have every feature I loved from Android but it's 100x smoother and more reliable. I don't regret the move.
I'm not at all surprised by this. For a 5 year span I used probably 4-5 different Android phones, from HTC & Samsung. All of them had this kind of glitch, where some kind of race condition gets the system stuck in an unanticipated state. UI elements that were supposed to scroll smoothly off the screen would get stuck halfway. Some system app would lock out touch events temporarily while loading something, and it would stay locked until a hard reboot.
I think it's a symptom of a system that's designed as a stack of abstraction layers, with developers who don't communicate. The developers of project A think a bug is a minor issue, not knowing that project B relies on it for something critical.
It's hard to write an app for a platform like this, too. Instead of one cohesive target, you have discontinuous abstraction layers.
Looks like Microsoft Teams was part of the problem here. I assume they had to hook into some semi-documented functionality that Google wasn't aware of or thought no one would use. On iOS, where Apple keeps tight control over their API surface, this is less likely to happen.
Android has the concept of an Intent[0] which are basically a category of apps that can fulfill a functionality like sending an email, browsing the internet, or dialing a number, etc.
So a developper can create contacts/caller app so that for example, when you click on a call button from say a google search, the OS asks the user to pick one app that was declared to be able to ACTION_CALL.
If I had to guess, I'd say it's something having to do with Teams being given priority on calls followed by failure to having priority for emergency calls and no way to gracefully recover.
Quickly browsing the documentation I see comments like
Note: there will be restrictions on which applications can initiate a call; most applications should use the ACTION_DIAL.
Note: this Intent cannot be used to call emergency numbers. Applications can dial emergency numbers using ACTION_DIAL, however.[1]
I have yet to use any system where the UI can’t get stuck. Usually any menu/whatever that appears on mouse over will remain open when some other action overlays another GUI element over it. But there are myriad other small bugs like this on windows to ios to even tiny tiling wms.
A similar thing happened to me a few years ago when calling the Swedish equivalent (112). As soon as the operator picked up the dialer just crashed and there was no trace of the call in the log.
I did this three times before switching to a friend's phone. I don't remember what apps I had or even what phone it was (except being Android) but it was a pretty bizarre and scary experience.
I see a lot of bashing of teams for touching the dialer. Please take a look at https://www.fcc.gov/mlts-911-requirements before you say that they should not touch the dialer.
Yes they royally f'd up. However Teams is a voip carrier among other things. As of Jan. 6, 2022 they are not allowed to ignore 911 anymore. They HAVE to allow 911 calls. Even being a non fixed device. And on android this does mean interacting with the dialer.
(I have no affiliation with google or microsoft. I however did switch our small company to voip earlier this year and had to take a deep dive into the legalities.)
(In advance, I apologize if this seems unnecessarily harsh, but it is description of a real event and the thought process of younger me)
Unrelated, but in 2012 or something like that, I was out walking, on my way to a meeting. I literally stopped mid walk, and turned another direction, went to a store and bought an iPhone.
My, at the time, state of the art Samsung galaxy S3 had just prevented me from answer an incoming call due to a software bug. As the S3 froze and then crashed, a crushing realization hit me; what I was holding wasn't a phone, but something else. I was even a poor student at the time, but due to engagements, I was completely dependent on my phone working, or as I then realized: "Having a phone".
Not being able to call emergency services with a phone is completely unacceptable.
I am only posting to add that with my pixel 3 I am having issues with incoming calls being dropped or the interface not allowing me to accept an incoming call. Especially since the new re-design of the caller app a few months ago. Even an old phone should always be able to call and accept calls.
Due to the emergency use-cases, I really think call functions should be the highest priority of smart phones and I cannot understand why there is so much sloppiness in QA with this. There is going to be kids out there that try to call their parents and their calls get dropped, same with elderly or otherwise vulnerable. You don't always want then to call 911 as first resort. But hopefully they remember to do it if cannot get through to their carer..
Before people suggest it, getting a second phone that guarantees handling incoming calls in not practical, as they would have to dial a different number than usual in an emergency.
Android is traditionally an open system that allows you to mess with the system in all sorts of ways. I've previously replaced the default launcher and I know that you can replace the default lock screen if you want to. But that means that you can install a lock screen that prevents people without your password from making emergency calls, here's the first set of instructions I found Googling it.
Normally I feel like it's a strength of the Android operating system that users are allowed to make whatever changes they want, including handing off all responsibility for phone calls to Microsoft or whatever. But in cases like this where users might not understand what that means I wonder how we can put in better guardrails while still maintaining the systems flexibility.
One more reason to give to people when they ask me why I don't want to use Microsoft Teams. What shitshow that product is. Besides being so unreliable that it is unusable for its intended purpose it is invasive to a degree that insults me as a person that tries to have a reasonable degree of control over the software executing on my machines.
Lot of people making comments about Google and Android here, and I can understand why, but they aren't the only company who make an operating system where Teams interacts unfavourably with the core OS.
No matter how many Windows updates I install, or how many times I update drivers and firmware, Teams on Windows 10 on my Dell laptop is a very unstable combination. When on video calls it causes problem conditions in the graphics drivers that destabilise Teams, sometimes other applications such as Firefox, and will fairly regularly bluescreen the OS.
Again on video calls it also interacts poorly with Killer WiFi drivers leading to:
- intermittent drop-outs in network connectivity affecting all applications, including Teams (but not other devices on my network),
- total loss of WiFi connection, requiring disable/reenable of my wireless network adapter, and occasionally a machine reboot to resolve
- again, OS bluescreens
These problems only happen during Teams video calls, and most regularly (though not always) after the system has slept and woken at least once since its last reboot.
I'm not even going to dive in to the multitude of application level problems (failing to load calendar, failing to join meetings, breaking copy & paste, and on, and on). My point is that, as much as Google is at fault here, so is Microsoft: Teams is not good software. It is not built with safe interaction with the OS in mind, and it is not well tested.
Feature-wise Teams is far and away ahead of alternatives such as Zoom, and call quality is generally better than some alternatives, such as Google Hangouts, but it's let down by poor engineering and, as I've already said, inadequate testing. In the case of OP, with very serious results.
How is this issue only related to Pixel phones? If the issue is in the platform level and Teams app (or other apps that act as catalyst to this issue), how are other manufacturer phones safer?
I couldn't understand this point on why only Pixel users are affected?
I would say, accidentally dialing 911 is somewhat more acceptable than the current issue in discussion. One thing that sounds unacceptable is, Google expecting this issue to be fixed by MS Teams. At least their response should be accepting the situation and providing a security fix asap.
I've had a similar issue where no interaction worked and then physical buttons have a long-press to dial emergency. I just stayed quiet and 911 recognized it as a pocket dial and hung up.
[+] [-] Animats|4 years ago|reply
The FCC regulates 911 service. Here's the form for filing a complaint about 911 service:
https://consumercomplaints.fcc.gov/hc/en-us/requests/new?tic...
States also regulate 911 service. Try your state's office of emergency services.
There's something called "Kari's Law" that may apply here. This was passed in 2018 after someone was being attacked in a hotel room and their 9 year old daughter tried to call 911. She couldn't get through because the phone system required dialing 9 for an outside line. So, now, all business phone systems are required to recognize and pass through 911 to the main phone network. There are criminal penalties. (Microsoft might argue that "Teams" is not a "multi-line telephone system". That probably wouldn't go far with a jury. The clear intent of the law is that if you interpose something between a phone handset and the 911 network, it has to pass through 911 calls.)
The whole 911 area is heavily regulated, since it requires that so many things interoperate reliably.
[+] [-] LurkersWillLurk|4 years ago|reply
> We determined that the issue was being caused by unintended interaction between the Microsoft Teams app and the underlying Android operating system.
As someone whose organizational policy signs my Teams client out after a couple hours of inactivity, I would love to know how on earth this is possible. I truly am at a loss, and I am furious at the thought that I have been unable to dial 911 for who knows how long.
At least I know the ten digit number for my local emergency services, but the average person probably doesn't. This is unacceptable.
[+] [-] bit_logic|4 years ago|reply
And they mentioned an Android update, but what about the millions of Android phones that aren't getting regular updates? Does that mean there's potentially millions of phones that can't dial 911?
I like Pixel and Android, but am seriously thinking of switching to iphone because I really need a phone I can trust will dial 911 when I need it.
[+] [-] nneonneo|4 years ago|reply
Let’s not forget - someone very nearly could have died thanks to this glitch. Thankfully, a landline was available.
[+] [-] nobrains|4 years ago|reply
Initially I thought the above comment was unreasonable. But when I put myself in the same shoes, I have the EXACT same feeling.
It is like the person who was coming at the intersection at blaring speed, but missed me. The fact that he COULD have hit me, and if that happened, I would likely have died, is a very frustrating thought. But when conveying it to a 3rd party, I feel the 3rd party might think "hey, its ok. nothing happened. you are safe. he did not hit you, so why are you upset?"
[+] [-] ranma42|4 years ago|reply
[+] [-] georgemcbay|4 years ago|reply
A third-party app causing this issue on accident means a third-party app could cause this issue maliciously and any app not part of the base operating system should not be capable of causing an issue interfering with emergency calling.
I assume/hope their January 4th fix addresses whatever the issue is at a more fundamental level, but this seems like the sort of thing that should be addressed a lot sooner than a month out.
[+] [-] mrjin|4 years ago|reply
[+] [-] INTPenis|4 years ago|reply
[+] [-] utrack|4 years ago|reply
[+] [-] ls15|4 years ago|reply
Why can't we have open standards for communication in 2021, where everyone can just use the software that they trust? I would never use teams if I had a choice, besides looking for another job.
[+] [-] tiagod|4 years ago|reply
[+] [-] unknown|4 years ago|reply
[deleted]
[+] [-] facorreia|4 years ago|reply
[+] [-] bergwerf|4 years ago|reply
As for this issue. All I can think of is the tragedies it may cause. It's a cliché: software developers are not responsible, except when their PR forces them to take action.
[+] [-] JohnWhigham|4 years ago|reply
Software didn't have to be this way...
[+] [-] mFixman|4 years ago|reply
I see feature creep and sloppy functionality in the core as a symptom of the usual tech project management style, where there's pressure to make up random metrics to have flashy results over maintaining existing functionality.
Proper testing has the same impact for your performance than just ignoring the metrics you are supposed to test. You can also get praised when you fix the problem your sloppiness caused.
[+] [-] lm28469|4 years ago|reply
I can't stand that anymore. Every single updates make things more and more unusable, they hide settings, they make buttons bigger for no reasons, &c.
They even managed to butcher the alarm app... it looks like an app designed for visually impaired people (which would be fine if it was an option and not the default/only choice).
[+] [-] petee|4 years ago|reply
I've experienced the severe decline in stability over the last 10 years of use, and on flagship phones, not outdated.
Currently my Pixel sometimes displayes an open app partially off screen, or scaled wrong and clipped --- this is basic UI that worked for years and is now broken again.
[+] [-] cesarb|4 years ago|reply
"Based on our investigation [...] We determined that the issue was being caused by unintended interaction between the Microsoft Teams app and the underlying Android operating system. [...] 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. [...]"
Now I'm really curious as to what that "unintended interaction" was.
[+] [-] niyazpk|4 years ago|reply
No customization done by the user, including installation of apps should prevent a user from being able to call 911, period.
[+] [-] ppg677|4 years ago|reply
The phone's callstack takes a lot of special actions when calling 911, including locking onto any tower even if it is not in the preferred roaming list. As with many exceptional conditions, these code paths are often not as well tested.
[+] [-] blep-arsh|4 years ago|reply
[+] [-] noja|4 years ago|reply
"We believe the issue is only present on a small number of devices" -> Reads like damage limitation. Don't believe it, say why!
"we are currently only aware of one user report" -> Irrelevant. Damage limitation. Don't ever write this. Most users will never be able to recognise it as an Android problem, even fewer will have the ability to bug report it.
-- https://www.reddit.com/r/GooglePixel/comments/r4xz1f/pixel_p...
[+] [-] uyt|4 years ago|reply
[+] [-] sumitgt|4 years ago|reply
I don't think it affects finding that device from other devices.
[+] [-] Farbklex|4 years ago|reply
[+] [-] cett|4 years ago|reply
[+] [-] kevin_thibedeau|4 years ago|reply
[+] [-] habosa|4 years ago|reply
I bought myself a $400 iPhone SE. It may not have every feature I loved from Android but it's 100x smoother and more reliable. I don't regret the move.
[+] [-] phendrenad2|4 years ago|reply
I think it's a symptom of a system that's designed as a stack of abstraction layers, with developers who don't communicate. The developers of project A think a bug is a minor issue, not knowing that project B relies on it for something critical.
It's hard to write an app for a platform like this, too. Instead of one cohesive target, you have discontinuous abstraction layers.
Looks like Microsoft Teams was part of the problem here. I assume they had to hook into some semi-documented functionality that Google wasn't aware of or thought no one would use. On iOS, where Apple keeps tight control over their API surface, this is less likely to happen.
[+] [-] macromagnon|4 years ago|reply
So a developper can create contacts/caller app so that for example, when you click on a call button from say a google search, the OS asks the user to pick one app that was declared to be able to ACTION_CALL.
If I had to guess, I'd say it's something having to do with Teams being given priority on calls followed by failure to having priority for emergency calls and no way to gracefully recover.
Quickly browsing the documentation I see comments like
Note: there will be restrictions on which applications can initiate a call; most applications should use the ACTION_DIAL.
Note: this Intent cannot be used to call emergency numbers. Applications can dial emergency numbers using ACTION_DIAL, however.[1]
[0] https://developer.android.com/guide/components/intents-commo...
[1] https://developer.android.com/reference/android/content/Inte...
[+] [-] fshbbdssbbgdd|4 years ago|reply
I snorted when I read this. Trust me, iOS has plenty of broken and poorly-documented APIs.
[+] [-] kaba0|4 years ago|reply
[+] [-] varjag|4 years ago|reply
[+] [-] hopfog|4 years ago|reply
I did this three times before switching to a friend's phone. I don't remember what apps I had or even what phone it was (except being Android) but it was a pretty bizarre and scary experience.
[+] [-] mongol|4 years ago|reply
[+] [-] birdman3131|4 years ago|reply
Yes they royally f'd up. However Teams is a voip carrier among other things. As of Jan. 6, 2022 they are not allowed to ignore 911 anymore. They HAVE to allow 911 calls. Even being a non fixed device. And on android this does mean interacting with the dialer.
(I have no affiliation with google or microsoft. I however did switch our small company to voip earlier this year and had to take a deep dive into the legalities.)
[+] [-] pcmoney|4 years ago|reply
And yes calling 911 is “the basics”
[+] [-] Cort3z|4 years ago|reply
Unrelated, but in 2012 or something like that, I was out walking, on my way to a meeting. I literally stopped mid walk, and turned another direction, went to a store and bought an iPhone.
My, at the time, state of the art Samsung galaxy S3 had just prevented me from answer an incoming call due to a software bug. As the S3 froze and then crashed, a crushing realization hit me; what I was holding wasn't a phone, but something else. I was even a poor student at the time, but due to engagements, I was completely dependent on my phone working, or as I then realized: "Having a phone".
[+] [-] prennert|4 years ago|reply
I am only posting to add that with my pixel 3 I am having issues with incoming calls being dropped or the interface not allowing me to accept an incoming call. Especially since the new re-design of the caller app a few months ago. Even an old phone should always be able to call and accept calls.
Due to the emergency use-cases, I really think call functions should be the highest priority of smart phones and I cannot understand why there is so much sloppiness in QA with this. There is going to be kids out there that try to call their parents and their calls get dropped, same with elderly or otherwise vulnerable. You don't always want then to call 911 as first resort. But hopefully they remember to do it if cannot get through to their carer..
Before people suggest it, getting a second phone that guarantees handling incoming calls in not practical, as they would have to dial a different number than usual in an emergency.
[+] [-] Symmetry|4 years ago|reply
https://www.thecustomdroid.com/remove-emergency-call-button-...
Normally I feel like it's a strength of the Android operating system that users are allowed to make whatever changes they want, including handing off all responsibility for phone calls to Microsoft or whatever. But in cases like this where users might not understand what that means I wonder how we can put in better guardrails while still maintaining the systems flexibility.
[+] [-] jacquesm|4 years ago|reply
[+] [-] bartread|4 years ago|reply
No matter how many Windows updates I install, or how many times I update drivers and firmware, Teams on Windows 10 on my Dell laptop is a very unstable combination. When on video calls it causes problem conditions in the graphics drivers that destabilise Teams, sometimes other applications such as Firefox, and will fairly regularly bluescreen the OS.
Again on video calls it also interacts poorly with Killer WiFi drivers leading to:
- intermittent drop-outs in network connectivity affecting all applications, including Teams (but not other devices on my network),
- total loss of WiFi connection, requiring disable/reenable of my wireless network adapter, and occasionally a machine reboot to resolve
- again, OS bluescreens
These problems only happen during Teams video calls, and most regularly (though not always) after the system has slept and woken at least once since its last reboot.
I'm not even going to dive in to the multitude of application level problems (failing to load calendar, failing to join meetings, breaking copy & paste, and on, and on). My point is that, as much as Google is at fault here, so is Microsoft: Teams is not good software. It is not built with safe interaction with the OS in mind, and it is not well tested.
Feature-wise Teams is far and away ahead of alternatives such as Zoom, and call quality is generally better than some alternatives, such as Google Hangouts, but it's let down by poor engineering and, as I've already said, inadequate testing. In the case of OP, with very serious results.
[+] [-] codetiger|4 years ago|reply
[+] [-] WoodenChair|4 years ago|reply
[+] [-] codetiger|4 years ago|reply
[+] [-] blep-arsh|4 years ago|reply
[+] [-] liveoneggs|4 years ago|reply
[+] [-] Dylan16807|4 years ago|reply