What’s New in 2.0.0 • DFU / Recovery boot identity — When a Mac, iPhone or iPad is in DFU or Recovery mode, see its chip and model, board ID, chip revision and fuse mode, decoded from what the device publishes over USB. • DFU port guide for the newest Macs — Adds MacBook Pro, MacBook Air and Mac Studio with M5, Mac mini with M5 Pro and M6, and MacBook Neo, following Apple’s September 2026 chart. Mac mini (2024) explains a wording change in Apple’s chart. • Live hub port status — USB hub detail now shows the hub’s real port count and which ports have a device connected. • Interfaces and endpoints for every device — Read from the descriptor macOS cached at enumeration, without opening or seizing the device. • USB-C ports refresh on their own — Plugging or unplugging a cable, charger or device now updates the USB-C Ports pane straight away. • More careful E-Marker reading — A cable’s Extended Power Range flag is now checked against its 5 A / 50 V ratings, and a cleared flag reads “not declared” rather than “no”. • Stability — Fixes a crash when closing a window while a dock or hub was still connecting, and makes hotplug handling lighter. Still 100% local and read-only. No accounts, no cloud.

• DFU port (this Mac) — Shows Apple’s published revive/restore USB-C location for your Mac model, with cable rules. Helps you pick the right port when recovering an Apple device. No invented PortNumber ↔ DFU mapping. • Full PDOs / PD contract + DP Alt Mode — Advertised power options and the winning contract from IORegistry, plus DisplayPort Alt Mode Supported / Provisioned / Active (lanes/rate when published). Empty when macOS has not published a power source. • Android USB Protection coach — Charge-only / lock-screen USB Protection unlock + reconnect guidance from interface descriptors; short tip only for ADB over Wi‑Fi (no pairing UI). • Accessibility IDs — Stable iusb.* identifiers so automation and AI tools can drive USB inspection UI. Still 100% local and read-only. No accounts, no cloud.

• Apple USB modes • Port charging (DFP) — On device and USB-C port details, • Broader Android recognition — More OEM vendor IDs and name tokens; charge-only and USB-tether modes stay visible in the Android list. • Stability — IOKit iterator drains on HPM/hub matching, PD monitor start/stop on hotplug, and non-blocking hub port power cycling. Still 100% local and read-only. No accounts, no cloud.

DEBUG READINESS FOR IPHONE AND ANDROID Open an Apple or Android device and see whether Xcode, Finder or adb can reach it over USB right now — and which check failed if not. The scorecard covers the debug channel (usbmux or ADB), negotiated link speed, and hub path depth, with copy-ready log show / adb commands. MORE RELIABLE HOTPLUG USB-C Power Delivery cable and device monitors, and Thunderbolt monitoring, now receive attach and detach on a background queue like the USB tree already did, so a dock burst no longer contends with scrolling the UI.

USB-C PORT PANEL Every built-in USB-C port now shows what it negotiated, in the order the negotiation happens: what the port supports, what it agreed with the attached device, and what is actually carrying data. Reading down those three rows is the diagnosis. Everything active is working as intended. A transport that was agreed and never activated means the link failed to train — a fault the device list cannot show you, because the device still appears, just slower than it should be. A transport the port supports but never offered is usually the attached device's own limit rather than the port's: a phone with no USB 3, or a charge-only cable. The panel also reports plug orientation, active and optical cable flags, DisplayPort pin assignment, hot-plug detect, controller firmware, and running counts of plug events, connections and overcurrent faults. A plug count climbing on a cable nobody is touching is a failing connector, and an overcurrent count above zero is a hardware fault that was previously invisible. All of it is read from the port controller itself. No device is opened and nothing is sent to the attached hardware. CONNECTION MODE Apple and Android devices now show what they are actually doing over the cable, read from the interface descriptors they publish. An iPhone reports whether the usbmux, photo and network interfaces are present, so "no usbmux interface — Xcode and Finder cannot reach this device" replaces a silent absence. Android devices report ADB, file transfer, photo transfer, accessory mode and tethering the same way. When nothing is carrying data, the panel says what to change: unlock the device, accept the Trust prompt, switch the USB mode on the phone, or try a cable that has data lines. A Billboard interface is called out on its own — a device publishes one instead of a working function, which is the device telling you this cable or port will not carry the alternate mode it asked for. CONTROLLERS ON A DOCK NOW APPEAR A Thunderbolt dock or PCIe card whose USB host controllers arrive with nothing attached to them was missed entirely, because only USB devices were being watched. Docking a sixteen-port charging hub brought up four host controllers that did not show until Refresh was pressed. Host controllers are now watched directly, and one arriving or leaving triggers a full re-enumeration. ACCESSIBILITY Device rows are now a single element carrying vendor, link generation and PCI identifiers, instead of fragments a screen reader had to reassemble. The speed and generation badges especially were invisible to anyone not looking at the screen.

ANDROID DEVICES Android phones and tablets now have their own sidebar section, alongside Apple Mobile Devices. LIVE USB ENDPOINTS Select a device to see each interface's endpoints: address, direction, transfer type, max packet size, interval, and SuperSpeed / SuperSpeedPlus companions when present. Values come from the configuration descriptor IOKit already cached at enumerate time. The app never opens or seizes the device to read them, so ADB, MTP and the real USB link stay undisturbed. WHEN A DEVICE IS BUSY If the descriptor is not readable because a kernel driver or user client holds the device, the pane shows the I/O Registry exclusive owner and any claimed interfaces — the same public properties System Information uses — instead of failing silently. HOTPLUG AND HUB TREE Arrive and leave updates are smoother. Downstream Android devices are no longer shown as if they were the hub. USB SPEED The negotiated link speed is still reported honestly. When a device's bcdUSB is 3.x but the link is High Speed (common on dual-bus hubs), the UI notes that the device is USB 3.x capable.

CORRECTED USB-C CABLE READINGS Every figure read from an e-marked cable — speed, current, maximum voltage and whether VCONN is required — was being taken from the wrong bits, and was wrong for every cable. All four are now read where the USB Power Delivery specification puts them, and decoding follows the revision the port negotiated, because the layouts genuinely differ between PD 2.0 and PD 3.0. Where a revision defines no such field, it reads as unknown rather than being guessed, and maximum wattage appears only when the cable states both a voltage and a current. Re-timer, re-driver and optical cables are now told apart by the field that carries that information rather than by matching words in a summary string. Active Cable VDO 2 is decoded in full — operating and shutdown temperature, USB4 support, lane count and generation — alongside EPR mode, cable latency, termination type and plug type. Every field is shown with the bit range it came from, so you can check the app against the specification instead of taking its word. CONTROLLERS, HUBS AND VENDORS USB4, USB 3.x and USB 2.0 host controllers and hub chips are now identified by vendor and model, from a built-in database of 676 controllers and 351 hub chips. The USB tree, the Thunderbolt list and the hub list show the vendor with a generation badge, and controllers reached over Thunderbolt or USB4 are marked as external — so it is clear when a branch of the tree lives in a dock rather than in the Mac. Hubs that publish no name of their own, which is most of them, are identified from their chip instead of appearing as a bare IOKit class with every attached device parented under it. SYSTEM LOG Select a host controller, hub or device and iUSBDebugger shows the macOS system log for just that selection. Messages are matched by USB location ID, so a controller covers its whole bus and a hub covers itself plus every downstream port. Attach, detach, port power, I/O error, reset and link events are classified and colour-coded, with failure codes shown as badges. macOS does not allow apps from the App Store to read the system log directly. The tab explains how to export it with a single command, shows that command with a copy button, and opens the file you save — every filter, badge and location match works the same on imported lines. Choosing the file is what grants access to it; the app can read nothing else, and nothing is sent anywhere. ENUMERATION YOU CAN TRUST The device tree updates as soon as something is plugged in or removed. Controller discovery no longer depends on knowing a controller's name in advance, so devices behind an external dock or a PCIe card are found, and every USB device the system knows about is accounted for in the tree. USB location IDs are decoded correctly. Port Route, Topology Depth and Parent Route are now right for every device, and the host controller is shown as its own field. Clicking an item in the sidebar always updates the details pane, selected rows highlight, and the pane follows the latest reading rather than a snapshot from when you clicked. CLEARER ABOUT WHAT IT DOES NOT KNOW Apple mobile devices no longer have a connector inferred from their negotiated speed, which carries no such information: a USB-C iPhone on a USB 2.0 cable enumerates exactly like a Lightning one. The connector is reported as USB-C when the port's Power Delivery identity proves it, and left unstated otherwise.

SYSTEM LOG Select a host controller, hub, or device and iUSBDebugger now shows the macOS system log for just that selection. Messages are matched by USB location ID, so a controller covers its whole bus and a hub covers itself plus every downstream port. Attach, detach, port power, I/O error, reset and link events are classified and colour-coded, with failure codes shown as badges. macOS does not allow apps from the App Store to read the system log directly. The tab explains how to export it with a single command, shows you that command with a copy button, and opens the file you save — every filter, badge and location match works the same on imported lines. Choosing the file is what grants access to it; the app can read nothing else, and nothing is sent anywhere. ACCURATE LOCATION IDS USB location IDs are decoded correctly. Previously the host controller number was folded into the port route, so a device on controller 20 port 2 was reported as a three-hop route, and root controllers appeared to sit one or two hops deep. Port Route, Topology Depth and Parent Route are now right for every device, and the host controller is shown as its own field. RELIABLE SELECTION Clicking an item in the sidebar always updates the details pane. Selecting a device while a hub was selected used to leave the hub on screen. Rows now highlight when selected, and the pane follows the latest reading instead of a snapshot from when you clicked, so it stays current as devices come and go. A TIDIER TOOLBAR Details and System Log moved into a switcher in the toolbar, next to Refresh and the last-updated time, which gives the detail views their full height. Refresh now waits for enumeration to finish, so the timestamp reflects data actually on screen.

SIMPLIFIED CHINESE The full interface — device names, cable and charger descriptions, Power Delivery and Thunderbolt details — now follows your system language. Spec identifiers such as "USB PD 2.0", "bcdDevice" and "SBU1/SBU2" keep their standard form. SELECTION NO LONGER RESETS Plugging or unplugging a device used to clear whatever you had selected in the sidebar, send the detail pane back to the welcome screen, and collapse the expanded USB device tree. Your selection and the tree's expanded state now survive a refresh. LIGHTER ON HOTPLUG Attaching a hub or dock triggered one full registry scan per device that appeared behind it — around forty scans for a ten-device dock. Those are now coalesced into a single pass, so busy docks settle noticeably faster. STABILITY Fixed a resource leak that accumulated for as long as the app stayed open, and corrected how USB and Power Delivery properties are read out of the IOKit registry. The Mac App Store build remains strictly read-only. Hub port power control and device reset are developer-build tools and are not part of the shipping app.

Thunderbolt & USB4 dock support • Hubs built into your Thunderbolt and USB4 docks now appear automatically, with live status for every port. See more of your hubs • Hubs that macOS manages directly — and previously couldn't be read — now show their full details and per-port status. Built for the latest macOS • USB-C chargers, docks, and cables are identified correctly on the newest version of macOS. Refreshed, easier-to-read design • The sidebar is now grouped by USB technology with clearer headings, so you can find what you're looking for at a glance. • A polished app version footer and a tidier "last updated" indicator. iUSBDebugger remains a fast, private, read-only inspector — everything stays on your Mac.

- Added VDO bit field decode -- detailed breakdown of ID Header, Cert Stat, and Product VDOs per USB PD 3.x specification - Added Google Pixel and Android device recognition with device name lookup, Google SVID info, and custom VDM command reference - Improved app stability and code quality - Cleaned up menu bar items for a more polished experience