What you need to know
- After LG, ZTE, and Ericsson, Sony has announced that it is pulling out of MWC 2020 over Coronavirus concerns.
- Sony's press conference will instead take place on February 24 as a video via its official YouTube channel.
- Amazon too has confirmed that it will not be participating at MWC 2020 due to the outbreak.
Update: February 10 9:18 AM ET:
TCL has joined the list of companies that have decided to scale back their press conferences at MWC 2020 due to the Coronavirus crisis. The company will, however, still attend MWC and exhibit its latest devices in its booth at the Fira Gran Via convention center.
Update on TCL’s presence at #MWC20. We hope to see you at our booth in Hall 3, Stand 3D11! pic.twitter.com/EYptRI6BlGUpdate on TCL’s presence at #MWC20. We hope to see you at our booth in Hall 3, Stand 3D11! pic.twitter.com/EYptRI6BlG— TCL Mobile (@TCLMobileGlobal) February 10, 2020February 10, 2020
Here's what the company said in a statement posted on its website:
Sony says it will now be announcing "exciting product news" at the scheduled time of 8:30 AM (CET) on February 24 via the official Xperia YouTube channel. The company is expected to introduce a few new phones at its press conference, including a 5G-enabled flagship phone powered by the Snapdragon 865 chipset.
Amazon too has decided to pull out from the Mobile World Congress due to the outbreak. GSMA, which is organizing the event, has issued a new statement about additional measures that are being put in place to ensure the safety of both attendees and exhibitors at MWC 2020. The new measures include a ban on travelers from the Hubei province, temperature screening, and requiring attendees to self-certify that they haven't been in contact with any person infected with Coronavirus.
At this point I think it is fair to say MWC will be postponed. I am calling it...
It will be a shame if its cancelled but health and safety takes priority always.
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.