IT

Samsung phones are randomly sending photos to contacts

Samsung phones are randomly sending photos to contacts

Some owners of Samsung phones say their devices have started spontaneously sending their photos to a random contact. It only became apparent after the recipient alerted them. Users only find out the photos have been sent when they're asked about it. Samsung has said it's now looking into the problem. Sending photos can be disabled entirely via Settings by disabling storage permissions for the Samsung Messages app. Users can also switch to other messaging apps.

Business Insider writes that the highly problematic bug is exclusive to the company's most recent phones, meaning the Galaxy S9 and Galaxy S9 Plus. A Reddit user expressed their concern by saying "This sounds like a nightmare for me as I have lots and lots of clients in my phone".

This bug doesn't seem to be affecting users outside the United States so it's quite likely that it does have something to do with RCS but we won't know that for sure until Samsung gets back to us with more information after looking into the matter. Other Reddit posters have said their wives or other people on their shared family plans have received similar messages from other phones including the Note 8. "However, there was record of it on mobile logs", one Redditor posted less than a week ago.

A Samsung spokesperson told The Verge it's "aware of the reports" and that its technical teams are 'looking into it'.

The 76ers prepare a trade package for Kawhi Leonard
If LeBron does not opt in to his contract with the Cleveland Cavaliers on Friday, he will become an unrestricted free agent. You remember, the report that had James texting the Warriors' Kevin Durant suggesting they play together on the Lakers?

Affected users are encouraged to contact Samsung directly until a fix is issued.

Some believe the problem stems from the conversion from the SMS messaging protocol to the new RCS (Rich Communication Services) on the native Samsung texting app. Samsung has acknowledged the problem and is working on it, but has not pointed to a cause.

The issue isn't specific to one mobile carrier alone, and users from different operators reported the same problem.