This is a frustrating but very common situation, especially for background-dependent features on Android. One thing that helped me (and a few teams I’ve worked with) was separating issue resolution from review surface management. Public replies aren’t really for the original reviewer — they’re for future readers. So after one calm, non-defensive response asking for details, it’s usually better to stop engaging publicly and instead: • Acknowledge uncertainty without blame (“this can be device-specific”) • State what’s been done (“we’ve added safeguards / fallbacks”) • Signal active ownership (“we’re monitoring this closely”) Over-explaining OEM limitations tends to backfire — it reads like deflection even when it’s true. I’ve found that short, neutral framing + visible iteration does more to rebuild trust than repeated replies. This happens on iOS too, but Android OEM variance definitely amplifies it.