Discuss hardware-specific topics related to Mac.

Posts under Mac tag

26 Posts

Post

Replies

Boosts

Views

Activity

Icon for some menu items cannot be removed on macOS 26
create a sample XCode project using Objective-C and stroybook (xib) using latest XCode beta open MainMenu.xib, and select Main Menu → File → Print... remove the image like below 4. build it 5. run it on macOS 26 beta 7 6. The menu item "print.." still have "Image" Is there any way to remove image for one menu item. I have also tried NSMenuItem.image = nil, but still not work. The issue I met on my own app is that I cannot remove icons for "Zoom In", "Zoom Out" and many other menu items, which makes the menu items not aligned properly.
1
0
617
Sep ’25
HomePod Mini Beta Device Issues: Power, Connectivity, USB Recognition
Hi! Short time lurker, and first time poster, but I will try to be as descriptive as possible. I have had my HomePod mini since 2021, and have been loving it. Recently, though, I am facing issues which have paralyzed it. Background: Running two HomePod Minis under a stereo pair on the same network in a room. Devices worked well, with the odd dropping of the sound once a while, not too big of an issue. Started running HomePod OS26 beta in July to see what the new updates have, and maybe if the audio issues would be resolved. Issue: Two weeks ago, the after the (then) latest update, there was a no response issue in the app. No big deal, let's just restart the HomePod pair. After restart, no bueno. I also got a new beta software update notification, so decided if I updated them both, the issue will probably be resolved. No dice. The issue persists. So I decided to pair the HomePods and factory reset them. Both HomePods disappeared from my home app. Regular behavior. Going to reset them with the old unplug for 30 s, replug into power, hold finger on the display had no issues for the first one. For the second HomePod, unplug, hold, and plug in. Problems. No display. Tried it a bunch of times, nothing. Waited a day, in case the capacitors needed to be discharged for it to do a cold boot. Nothing. Looking across the interwebs, I found that we can connect the HomePods to Macs, have them show up on Finder, and update from there. Connecting into the Mac, nothing. Waited for the caps to discharge before engaging again, nothing. Now, I fear I may have problems. So I scheduled a meeting at the Genius Bar. Genius Bar individual said no support as you are running beta software. We are not allowed to touch or diagnose those devices. They also said that there are no external facing endpoints for us to diagnose or check. I would have better luck with online Apple Support or over call with Apple Support. Okay, sounds good. Contacting Apple Support, they said that we will have to wait for the official release of HomePodOS 26 for us to support you, to which I agreed. During this time, I thought about seeing if I could troubleshoot and see if anything was coming out of the HomePod when connected to the Mac. So I wrote a script, querying and logging different aspects of the USB controller on the Mac and seeing what device connects. I removed all other USB devices connected to the Mac, and started the script. First, I connected and disconnected the HomePod a couple of times, and on the last connect, I left it in, and let the script record the readings. Reading the output told me that there was indeed a device that was connecting and disconnecting. Here are some of my findings: Port Readout Summary Apple's UVDM stack lights up on the Port-USB-C@2 (CC path, SOP) AppleUVDM driver tried to read identity VDOs, initially rejected, then carried on and the transport finished powering on successfully. Furthermore, the VDM read attempts itself are rejected, typical when the accessory is gating Apple specific commands The CC transport merged metadata for SOP with a 3-VDO identity set. The CC property change during the run indicates an active PD negotiations. USB link states also toggled on that port with driver status Ready Port-USB-C@2/SOP shows Vendor ID and Product ID (not sure if this is private information, so not sharing) Port-USB-C@1/SOP, the e-marker in the HomePod cable shows the same, with product type "Passive Cable" Only CC is flagged "TransportsActive" Apple's accessory authentication stack is present The USB speeds on the port flicker between Gen 3 and Gen 2, indicating to me some sort of handshake failing in the stack, which is preventing enumeration in the System Report and Finder This likely is indicating to me that the target isn't enumerating as a normal USB device, but rather as a USB-PD Vendor Defined Messaging (UVDM) protocol on the CC line. Furthermore, the signature is in a "hidden" service/update modes, which does not enumerate standard USB functions. So, having all this information available to me, I got on a call with Apple Support today, and they went through some of the troubleshooting steps and told me that they could neither escalate the issue (due to it being on a beta software that THEY DO NOT SUPPORT) nor remediate or troubleshoot the issue (as it is an accessory) and the only thing their support options say is to wipe the device, as it is something that is not supported. Upon my suggestion of this my USB logs being used to review the case, they said my personal USB logs would be detrimental towards my case. Their final recommendation was for me to reach out to Apple Developer support as I am running beta software on this HomePod Mini. So, here I am! I highly believe this is a Software issue, contrary to what Apple Consumer Support call representative indicated. All and any help/guidance and support is appreciated. All and any help in boosting the visibility of this issue on the forums would also be greatly appreciated. I have had these bad boys since my undergrad, and I would hate to lose one of them. For Apple Support, before you lock and close this post down and recommend I go to Apple Consumer Support, they said that they cannot help me, and consumer support steps start and end at resetting the device.
0
0
612
Sep ’25
EtreCheck (from Etresoft, Inc)
Hello I've noticed that this product, heavily promoted on the ASC forums for many years, is no longer available from the Apple App Store. Can anyone tell me the reason why the product is no longer supported? Friends have asked me if it is 'safe' to use. Is it? Note to moderator: If I'm asking in the wrong places, please redirect my question. Thank you.
9
0
5.3k
Aug ’25
The volume on diskN couldn't be unmounted because it is in use by process 0 (kernel)
I am on Macos Sequoia 15.5. I plugged in a brand new 8TB SanDisk SSD portable drive. I want to reformat it. Diskutility fails in this way: Erasing "SanDisk Extreme Pro 55AF Media" (disk6) and creating "NewDrive" Unmounting disk The volume on disk6 couldn't be unmounted because it is in use by process 0 (kernel) Couldn't open device. : (-69877) Operation failed… I have the drive ejected. I'm used to ejecting a drive, then unplugging it. The first time I tried this, DiskUtility complained that all sorts of processes were using it still, after I Ejected the drive (Bash, simctl, Code Helper, Word, kernel 0). So I closed all the process one by one, until only kernel proc 0 was remaining. Apparently it is not safe to simply eject a drive and then unplug it, as Eject "succeeds" but many processes still have the drive open. How do I format the drive?
1
0
524
Aug ’25
MacBook Air (M2, 2023) Randomly Freezes After Sleep – Black Screen with Cursor Only
Since a recent macOS update (around one month ago), I’ve been experiencing a random issue on my MacBook Air (2023, M2). After the device enters sleep mode and I try to wake it, sometimes the screen stays black with only the cursor visible. The issue occurs randomly — not every time — but frequently enough to impact daily use. The system becomes completely unresponsive, and the only recovery method is a forced restart (holding the power button). Steps to Reproduce: 1. Leave the MacBook idle until it enters sleep automatically. 2. Wait for 10–30+ minutes. 3. Attempt to wake it using the keyboard, trackpad, or by opening the lid. 4. Randomly, the system fails to wake properly: screen turns on, shows a black background with a movable cursor, but nothing else appears. Expected Result: The system wakes normally and restores to the previous desktop session. Actual Result: The system randomly freezes on a black screen with a visible cursor. No user interface or login prompt appears. Requires a hard restart. System Information: • Device: MacBook Air 13”, M2, 2023 • macOS Version: [Insert exact version, e.g., macOS Sonoma 14.5] • Issue Since: Around one month ago (possibly after latest macOS update) • Peripherals: [Mention any external devices if applicable] • Reproducibility: Random (approximately 30–50% of the time after longer sleep) Additional Notes: • Issue is not consistent; sometimes the system wakes as expected. • Occurs regardless of whether on battery or plugged in. • No external monitors or USB accessories are connected when this happens.
1
0
457
Jun ’25
Icon for some menu items cannot be removed on macOS 26
create a sample XCode project using Objective-C and stroybook (xib) using latest XCode beta open MainMenu.xib, and select Main Menu → File → Print... remove the image like below 4. build it 5. run it on macOS 26 beta 7 6. The menu item "print.." still have "Image" Is there any way to remove image for one menu item. I have also tried NSMenuItem.image = nil, but still not work. The issue I met on my own app is that I cannot remove icons for "Zoom In", "Zoom Out" and many other menu items, which makes the menu items not aligned properly.
Replies
1
Boosts
0
Views
617
Activity
Sep ’25
HomePod Mini Beta Device Issues: Power, Connectivity, USB Recognition
Hi! Short time lurker, and first time poster, but I will try to be as descriptive as possible. I have had my HomePod mini since 2021, and have been loving it. Recently, though, I am facing issues which have paralyzed it. Background: Running two HomePod Minis under a stereo pair on the same network in a room. Devices worked well, with the odd dropping of the sound once a while, not too big of an issue. Started running HomePod OS26 beta in July to see what the new updates have, and maybe if the audio issues would be resolved. Issue: Two weeks ago, the after the (then) latest update, there was a no response issue in the app. No big deal, let's just restart the HomePod pair. After restart, no bueno. I also got a new beta software update notification, so decided if I updated them both, the issue will probably be resolved. No dice. The issue persists. So I decided to pair the HomePods and factory reset them. Both HomePods disappeared from my home app. Regular behavior. Going to reset them with the old unplug for 30 s, replug into power, hold finger on the display had no issues for the first one. For the second HomePod, unplug, hold, and plug in. Problems. No display. Tried it a bunch of times, nothing. Waited a day, in case the capacitors needed to be discharged for it to do a cold boot. Nothing. Looking across the interwebs, I found that we can connect the HomePods to Macs, have them show up on Finder, and update from there. Connecting into the Mac, nothing. Waited for the caps to discharge before engaging again, nothing. Now, I fear I may have problems. So I scheduled a meeting at the Genius Bar. Genius Bar individual said no support as you are running beta software. We are not allowed to touch or diagnose those devices. They also said that there are no external facing endpoints for us to diagnose or check. I would have better luck with online Apple Support or over call with Apple Support. Okay, sounds good. Contacting Apple Support, they said that we will have to wait for the official release of HomePodOS 26 for us to support you, to which I agreed. During this time, I thought about seeing if I could troubleshoot and see if anything was coming out of the HomePod when connected to the Mac. So I wrote a script, querying and logging different aspects of the USB controller on the Mac and seeing what device connects. I removed all other USB devices connected to the Mac, and started the script. First, I connected and disconnected the HomePod a couple of times, and on the last connect, I left it in, and let the script record the readings. Reading the output told me that there was indeed a device that was connecting and disconnecting. Here are some of my findings: Port Readout Summary Apple's UVDM stack lights up on the Port-USB-C@2 (CC path, SOP) AppleUVDM driver tried to read identity VDOs, initially rejected, then carried on and the transport finished powering on successfully. Furthermore, the VDM read attempts itself are rejected, typical when the accessory is gating Apple specific commands The CC transport merged metadata for SOP with a 3-VDO identity set. The CC property change during the run indicates an active PD negotiations. USB link states also toggled on that port with driver status Ready Port-USB-C@2/SOP shows Vendor ID and Product ID (not sure if this is private information, so not sharing) Port-USB-C@1/SOP, the e-marker in the HomePod cable shows the same, with product type "Passive Cable" Only CC is flagged "TransportsActive" Apple's accessory authentication stack is present The USB speeds on the port flicker between Gen 3 and Gen 2, indicating to me some sort of handshake failing in the stack, which is preventing enumeration in the System Report and Finder This likely is indicating to me that the target isn't enumerating as a normal USB device, but rather as a USB-PD Vendor Defined Messaging (UVDM) protocol on the CC line. Furthermore, the signature is in a "hidden" service/update modes, which does not enumerate standard USB functions. So, having all this information available to me, I got on a call with Apple Support today, and they went through some of the troubleshooting steps and told me that they could neither escalate the issue (due to it being on a beta software that THEY DO NOT SUPPORT) nor remediate or troubleshoot the issue (as it is an accessory) and the only thing their support options say is to wipe the device, as it is something that is not supported. Upon my suggestion of this my USB logs being used to review the case, they said my personal USB logs would be detrimental towards my case. Their final recommendation was for me to reach out to Apple Developer support as I am running beta software on this HomePod Mini. So, here I am! I highly believe this is a Software issue, contrary to what Apple Consumer Support call representative indicated. All and any help/guidance and support is appreciated. All and any help in boosting the visibility of this issue on the forums would also be greatly appreciated. I have had these bad boys since my undergrad, and I would hate to lose one of them. For Apple Support, before you lock and close this post down and recommend I go to Apple Consumer Support, they said that they cannot help me, and consumer support steps start and end at resetting the device.
Replies
0
Boosts
0
Views
612
Activity
Sep ’25
Xcode beta RC missing “Mac (Designed for iPad)” option in preview
I’m using the latest Xcode beta RC(Version 26.0 (17A321)), and when I try to preview my SwiftUI views, the “Mac (Designed for iPad)” option is missing from the preview device list.
Replies
0
Boosts
0
Views
289
Activity
Sep ’25
EtreCheck (from Etresoft, Inc)
Hello I've noticed that this product, heavily promoted on the ASC forums for many years, is no longer available from the Apple App Store. Can anyone tell me the reason why the product is no longer supported? Friends have asked me if it is 'safe' to use. Is it? Note to moderator: If I'm asking in the wrong places, please redirect my question. Thank you.
Replies
9
Boosts
0
Views
5.3k
Activity
Aug ’25
The volume on diskN couldn't be unmounted because it is in use by process 0 (kernel)
I am on Macos Sequoia 15.5. I plugged in a brand new 8TB SanDisk SSD portable drive. I want to reformat it. Diskutility fails in this way: Erasing "SanDisk Extreme Pro 55AF Media" (disk6) and creating "NewDrive" Unmounting disk The volume on disk6 couldn't be unmounted because it is in use by process 0 (kernel) Couldn't open device. : (-69877) Operation failed… I have the drive ejected. I'm used to ejecting a drive, then unplugging it. The first time I tried this, DiskUtility complained that all sorts of processes were using it still, after I Ejected the drive (Bash, simctl, Code Helper, Word, kernel 0). So I closed all the process one by one, until only kernel proc 0 was remaining. Apparently it is not safe to simply eject a drive and then unplug it, as Eject "succeeds" but many processes still have the drive open. How do I format the drive?
Replies
1
Boosts
0
Views
524
Activity
Aug ’25
MacBook Air (M2, 2023) Randomly Freezes After Sleep – Black Screen with Cursor Only
Since a recent macOS update (around one month ago), I’ve been experiencing a random issue on my MacBook Air (2023, M2). After the device enters sleep mode and I try to wake it, sometimes the screen stays black with only the cursor visible. The issue occurs randomly — not every time — but frequently enough to impact daily use. The system becomes completely unresponsive, and the only recovery method is a forced restart (holding the power button). Steps to Reproduce: 1. Leave the MacBook idle until it enters sleep automatically. 2. Wait for 10–30+ minutes. 3. Attempt to wake it using the keyboard, trackpad, or by opening the lid. 4. Randomly, the system fails to wake properly: screen turns on, shows a black background with a movable cursor, but nothing else appears. Expected Result: The system wakes normally and restores to the previous desktop session. Actual Result: The system randomly freezes on a black screen with a visible cursor. No user interface or login prompt appears. Requires a hard restart. System Information: • Device: MacBook Air 13”, M2, 2023 • macOS Version: [Insert exact version, e.g., macOS Sonoma 14.5] • Issue Since: Around one month ago (possibly after latest macOS update) • Peripherals: [Mention any external devices if applicable] • Reproducibility: Random (approximately 30–50% of the time after longer sleep) Additional Notes: • Issue is not consistent; sometimes the system wakes as expected. • Occurs regardless of whether on battery or plugged in. • No external monitors or USB accessories are connected when this happens.
Replies
1
Boosts
0
Views
457
Activity
Jun ’25