Operating-system layers
Know whether the problem is the device, browser, app or OS.
Each platform has different privacy controls, native diagnostics and hardware limits. DeviceOK keeps those layers separate so troubleshooting starts in the right place.
Windows 11Windows device troubleshooting often has two permission layers: Windows Privacy & security controls and the browser/app's own selection or permission. Device Manager errors add a third source of evidence for detection/driver problems.
→macOSOn macOS, a browser or app may need explicit Privacy & Security permission for camera, microphone and screen recording. Apple Diagnostics is the correct handoff for internal Mac hardware that websites cannot inspect.
→AndroidAndroid can block camera or microphone at the device privacy-control level, the browser-app permission level, and the website permission level. Browser-visible tests are useful for media, touch and some sensors, while protected phone hardware needs OEM diagnostics.
→iPhone & iPadiOS/iPadOS hardware access is governed by app-level Privacy & Security controls plus the browser site's permission. DeviceOK can test browser-visible media/touch behavior, but native phone diagnostics and repairs remain Apple-controlled.
→ChromeOSChromeOS has operating-system privacy controls for camera and microphone in addition to Chrome site permissions. This makes permission troubleshooting especially important before treating Chromebook hardware as failed.
→LinuxLinux browser device behavior depends on the distribution, desktop environment, audio stack, permissions and browser. DeviceOK can still provide high-signal browser evidence, but OS remediation must follow the user's distribution documentation.
→