Troubleshooting and how to get help.
Scan can't find your TV. Confirm your phone and the Frame TV are on the same WiFi network (some routers split 2.4 GHz and 5 GHz into separate networks — they need to be the same one). Also verify the TV is in Art Mode, not just on. On iPhone, check the Local Network permission below first — without it, scanning fails silently. If it still doesn't show up, open Settings → Advanced and enter the TV's IP address manually (find it on the TV under General → Network → Network Status).
iPhone: the "Local Network" permission. iOS asks for Local Network access the first time Open Frame looks for a TV. If you tapped "Don't Allow", the app can't reach anything on your WiFi — scanning finds nothing and entering the IP manually fails, with no obvious explanation for either. Turn it back on in the iOS Settings app under Open Frame → Local Network (or Settings → Privacy & Security → Local Network → Open Frame), then reopen Open Frame.
"Connection refused" or the TV stops responding. If a different device (a TV remote app, another phone) is already connected to the TV, the TV may refuse new connections until that one disconnects. Close any other Frame TV apps and try again.
The app shows "Not connected" but the TV is on. Pull down on the Home screen to force a reconnect. If the TV's IP changed (DHCP rebound), the app will auto-rediscover it by device ID, but the first attempt after the change can take a few seconds.
"Auto-wake TV on launch" does nothing on iPhone. The wake signal is a broadcast packet, and iOS blocks those without a special entitlement from Apple, so on iPhone that switch is currently a no-op — turn the TV on with its remote first. It works as expected on Android.
HEIC photos don't upload. The app converts HEIC to JPEG automatically. If conversion fails, the most common cause is a very large source photo (24 MP+) running into device memory limits — try a different photo, or in Settings → Advanced lower the JPEG quality slider.
Portrait photos appear rotated on the TV. The original cause was fixed in version 1.0.1. iOS had a second, separate cause — the system image loader dropped the photo's orientation flag before the app could read it — fixed in 1.4.3. If you're on anything earlier, update.
Open Frame is free. Without the ad-free purchase you'll see a single banner at the bottom of the Home, Tips and Settings screens — never while cropping, uploading, or browsing the TV gallery. Uploads are never gated behind an ad.
Your privacy choices. Where privacy law requires it, Open Frame asks for your ad choices the first time it shows ads, on iPhone and Android alike. You can change them any time in Settings → Privacy choices; that row only appears where the choice applies, and not at all once you've removed the ads.
Removing the ads. Settings → "Remove ads" is a one-time $1.99 purchase that hides the banners for good on that store account. There's no subscription, and no other upsell anywhere in the app.
The ads came back, or you're on a new phone. Settings → "Restore purchases" re-checks your store account and restores the entitlement. That check also runs automatically on every app launch, so you'd normally only need the button if a launch-time restore failed. A purchase belongs to the store account that made it — it doesn't carry across from Google Play to the App Store, or the other way.
"Remove ads" gives an error. Make sure you're on the latest version from Google Play or the App Store, then try again: the app shows the store's own reason for the failure (Android builds before 1.4.3 showed only a generic "unexpected error"). If it still fails, send that exact wording through Report a Bug.
The fastest path is the in-app Report a Bug button (Settings → Report a Bug). It pre-fills your email with the app version, a snapshot of recent in-app log output, and your TV connection state — that's enough context to triage most issues.
If the in-app composer doesn't work on your device, email [email protected] directly with:
Open Frame collects no personal data — see the full privacy policy. Bug reports you send via the in-app Report a Bug button only contain the diagnostic context listed above; nothing is auto-collected without your action.