iMac is not charging my iPhone

Question

Level 1

20 points

iMac is not charging my iPhone

My iMac is not charging the iPhone it continuously beeps on and off. I tried support the other day they had me reset the phone and the issue did not resolve. Further the incident number provided isn't recognized so I can't get back to them. I believe it is an issue with the iMac over the devices. My iPad and work iPad do the same things. They won't charge steadily if its under 60%. They go charge...uncharge...charge....uncharge.... and so on both devices are using Apple cords. I have tried all ports flipped the cords upside down. Used the NES trick and blew the inside of the plug port.

Any other solutions? Anyone else have this issue?

If iTunes doesn't recognize your iPhone, iPad, or iPod - Apple Support

I used this site ^ but it didn't offer enough of a solution. iTunes does recognizes it in intervals as it connects and disconnects.

iPhone 6s Plus, iOS 11.4, null

Posted on Jul 7, 2018 11:15 AM

Reply

Answer 1

Best reply

Old Toad

Level 10

207,439 points

Jul 7, 2018 11:33 AM in response to Photofel

Try this: How to reset the System Management Controller (SMC) on your Mac ...

Also have you tried different USB Ports and cables?

Reply

Answer 2

iCare

Level 4

2,490 points

Jul 10, 2018 10:21 AM in response to Photofel

I've experienced similar things with my iPhone using a standard wall charger. In my case my iPhone's Lightning port had accumulated lint from my pocket that was preventing the Lightning connector from making contact. After carefully cleaning out the Lightning port on the iPhone the constant charge/no-charge buzzing went away. Although there doesn't seem to be an official document showing how to clean the port, I turned my iPhone off, then very carefully used compressed air from a can and a toothpick to dislodge the lint pile stuck jammed into the bottom of the port. You need to be VERY careful not to damage any of the contacts inside the port or you will face an expensive repair. Here's another discussion where they had similar issues and resolved it by cleaning the port:

Cleaning Lightning Port

Reply