A search of the internet gave many suggestions such as faulty cable, hardware issue, but this didn't make sense. Using the same cable I was able to connect to a Windows 10 notebook, access and copy off all the folders containing photos and also perform a full backup and upgrade to the latest version of iPadOS 14.3.
Using the MacBook Air I could literally do nothing with the iPad.
Since I knew there was nothing wrong with the iPad or cable, I did wonder if the issue may be the iPad was trying to draw more power than the MacBook Air would provide. The MacBook Air's battery isn't great even though it was fully charged and the MacBook Air was running with the power plugged in..
One of the things I wanted to do with the iPad Air 2 was to find out the battery health using coconutBattery on the MacBook Air. With the iPad continuously beeping this was not possible. The battery on the iPad Air 2 at that time was reading 75%. I decided to fully charge the iPad's battery and then see what would happen.
After fully charging the iPad Air 2 and connecting to the MacBook Air using the USB cable the beeping had gone and I was able to access the iPad Air 2 as normal. The iPad Air 2 battery was reading 88% capacity so there appeared to be no issue with the iPad Air 2..
Exactly what the problem was is hard to tell. The solution to access the iPad Air 2 was to fully charge the iPad, however it's not known if the connection was continue to work as the iPad's charge reduced. It does seem the iPad Air 2 was having a power issue with the cable. Perhaps there's a worn contact on the cable reducing the power/voltage available. Perhaps it's an issue with how much power the MacBook Air could provide. I don't know the exact reason but hopefully knowing how I got around the issue and that using a Windows 10 computer solved my problems, may help others.
Kelvin Eldridge
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.