![]() Plugging it in renders different output in Console.app which confirms that the iMac detects it as a USB device. This now has no effect for some reason, and the observed behaviour is the same whether plugged in or wireless. When the issue first started occurring, it could be solved by plugging the trackpad in via a lightning cable.This behaviour occurs even though the trackpad is fully charged.When the aforementioned ceasing-to-click occurs, the trackpad is still functional as a touch surface (mouse movement, multi-finger gestures), but is visibly laggy (as though the screen has a reduced refresh rate).Either ceases to click (through haptic feedback) and stays that way or continues to disconnect (stopping haptic feedback) and reconnect (re-enabling haptic feedback).Starts to disconnect after four to eight hours of use (if it has not been used for an extended period prior to switching on).I have tried to post this on Apple Communities, but upon doing so am told the following, which didn't end up resolving itself: Hopefully this can a) Help others out, and b) Get Apple's attention, which seems to be an impossible task even after spending thousands of dollars with a company that supposedly prides itself on service. I've seen similar issues throughout forums, but I believe that this problem requires more attention from Apple and have additional details to put forward on my end that I cannot find matches for through Google searches. The iMac itself and extended Magic Keyboard that I opted for work without issues, but the Magic Trackpad 2 that came with it is being horrendously troublesome. The SDP record are how Bluetooth devices tell the host computer what capabilities they support, and I think the OS caches these.I purchased an iMac (Retina 5K, 27-Inch, 2017, macOS 10.13.4, 4.2 GHz, 32GB, 3TB Fusion Drive) less than three weeks ago, and had it delivered by Apple here in distant, little New Zealand. I also noted that prior to my removing from the cache, that the Bluetooth Explorer was unable to pull down the device's SDP record (error 0x4). My other theory is that perhaps when the device lost connection that it did not get "put away" correctly. ![]() I'm not sure why caching a device would prevent re-connection - I've got a theory that it's something to do with Migration Assistant or upgrading from 10.7 to 10.8 - the device is recognized as cached but the cached info is out of date or has metadata applicable only either to the older computer or 10.7. Well worth signing up for ( Download "Hardware IO Tools for Xcode") I realize that not everybody has knowledge of or access to the (free!) Dev Tools at Apple, but if you know your way around you can often find some interesting tidbits. My new Macbook Pro (which was migrated from my older Mac Pro tower) failed to discover and connect to my trackpad this morning (despite having connected yesterday), so I used the Apple Developer tool called "Bluetooth Explorer.app", found and deleted the trackpad from the Device Cache, and walked through the Setup Trackpad steps in System Preferences.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |