LightBlog

lundi 5 décembre 2016

Blu phones will use Google’s OTA solution going forward

BLU-R1-HD-review-27

BLU-R1-HD-review-27

Blu, the US-based smartphone manufacturer, found itself in quite a jam a few weeks ago. The security firm Kryptowire discovered that a few of Blu's devices were sending user's personal data to a company in China.

To prevent more security incidents, Blu announced that it would start using Google's OTA update solution infrastructure of the backdoor-afflicted solution provided by Chinese company Adups. Speaking to PCMag, the CEO of the company, Sammy Ohev-Zion, confirmed this by saying, "Any new model that launches from December onwards will have Google's OTA application instead of Adups."

He also added that the company will not install third party applications onto their devices if it doesn't have the source code and doesn't understand exactly how they work.

See also:

BLU Vivo 6 Hands On and First Impressions

1 week ago

Blu has admitted that about 120,000 of its phones were affected by the security issue and were sending user sensitive data to China including, among others, text messages, call logs, and contacts. The R1 HD, the Energy X Plus 2, the Studio Touch, the Advance 4.0 L2, the Neo XL, and the Energy Diamond are the devices that are part of this fiasco.

"We have an email history with Adups saying we did not want that functionality on our devices, and they violated our request," he said. "We are a hard-working, American, family-owned business, and we are the last people on Earth that would engage in anything that would abuse our hard-earned customer relationship." — Sammy Ohev-Zion, Blu's CEO.

Blu has already fixed the issue with a software update but nevertheless the company's reputation took a massive beating. In addition, it might be facing a class-action lawsuit soon.

So, any thoughts on this matter? Would you buy a Blu smartphone considering they now use Google's OTA solution? Let us know in the comment section below.



from Android Authority http://ift.tt/2gY2EVb
via IFTTT

Aucun commentaire:

Enregistrer un commentaire