Usb keeps spamming "No usb connected/disconnected" on Samsung s8+

[AC Question]

So over the last few days I have been having a weird problem with my phone. It keeps spamming a message with "No usb connected/disconnected" and it's starting to get really annoying. It keeps my phone screen turned on at all times because of the message popping up. I have been googling around but can't seem to find a solution for it. I have recorded a video of it on screen that hopefully can show you guys what I'm talking about.

Any help is highly appreciated as this issue is starting to get really annoying and draining my battery as well as it keeps turning my screen on and off all the time.

 

[alinixa]

https://youtu.be/a7nkSC7B69w

 

[DJ Mac]

So over the last few days I have been having a weird problem with my phone. It keeps spamming a message with "No usb connected/disconnected" and it's starting to get really annoying. It keeps my phone screen turned on at all times because of the message popping up. I have been googling around but can't seem to find a solution for it. I have recorded a video of it on screen that hopefully can show you guys what I'm talking about.

Any help is highly appreciated as this issue is starting to get really annoying and draining my battery as well as it keeps turning my screen on and off all the time.

I had the same problem. It started shortly after I put one of those magnetic mounts on the back of the cover that stick to a metallic ball that you stick to the dash of your car. I took the magnetic bit off the cover and after a while it stopped doing the usb connected / usb disconnected thing (which was a real pain because it kept turning the screen on constantly).

Whilst it did do it for a few minutes a couple of days later, I gave the USB port a bit of a cleanout using some paper folded over and scraped out a bit of "dirt" and it has been ok since. This is NOT a software issue as the first thing I did after TWO DAYS of the phone having the problem was a FACTORY RESET and that did NOT fix it, hence I new it was a physical / hardware issue.

Regards,
Dean - Central Coast, Australia