Wyze Window Cam started showing white bar at bottom of large views

I’ve had a Wyze Windows Cam for about a month, and it has worked as expected.
It is running on a Moto G 2025 smartphone, on Android 16.

But a few days ago, any “large” view started displaying a white bar at the bottom, over the Wyze logo and date-time stamp.

In more detail, most portrait views display normally.
But if the phone is rotated to landscape view, whether Live, Events, or SD Card, that white bar appears.
Or, if in portrait view I double-tap to enlarge, that also gets the white bar.

On the Wyze web portal, the views are good.

And, in the Mumu Player Android emulator, on Android 15, running on a Windows 11 PC, every view is good. So the problem only occurs on the phone.

Past discussions of this topic tied this behavior to specific versions of the Android app.
So on Fri 09-04-26 I found I was on 3.21.0.955 (August 31, 2026), and manually updated to 3.21.1.962 (September 3, 2026). But the problem remained.
I have Camera firmware version 1.3.0.52.

I’ve power cycled the camera a few times, and also power cycled the phone, too, for good measure, as the problem seems Android related, but not really tied to a particular Wyze app.

Just to get some formal complaint registered, I did submit a log, just in case it might help the programmers, in case other people reported the same problem.

Are there further steps I should take, or will this get figured out at Wyze?
E.g., trying older app versions, like 3.20.0.941 (August 24, 2026) or 3.19.0.935 (August 11, 2026)?

Or is there some Android graphic subsystem at fault, that might get corrected as the phone gets updates?

Note that submitting a log won’t do anything without opening a ticket to go with it. It just goes into a black hole and gets discarded after a while.

Try clearing the app cache (within the wyze app and also within android settings for the wyze app). If that doesn’t help, maybe uninstall and reinstall the app. But before doing that (so you don’t lose the update history), see if you can see the update history of the app, if it updated right around when it started, and reinstalling doesn’t help, I’d try downgrading to the version from before the issue started (can get it off apkmirror.com). Could be some fluke related to the combo of the wyze app and the resolution of your phone.

I reported this in Wyze app 3.21 - Released 8/31/2026 - Wyze News - Wyze Forum

Response was

No idea when it will be fixed.

In that case might as well downgrade to the one just prior and disable auto updates until fixed.

Occurs on my OGs and looks like OG based cameras like the Window cam.

My V4 is fine and OGs are fine on my iPad.

Not a big enough issue for me to go through the downgrade process.

Strange, haven’t noticed it on my OGs (or v4 of Panv3s). I’m running the 3.21.1.962 on Android 14. Maybe it is related to certain screen resolutions.

Just checked one of my OGs and there is a white bar on the right side when in landscape mode. Been there for a little while, didn’t even think anything of it. But nothing covering the bottom or top and it isn’t covering the video (video is the same size it always was, just a bit of the black that is usually on both sides is white on the right).

There have been a number of UI issues with the android 3.21 update:

  • Favorites tab freezing (just fixed with 3.21.1.962)
  • Black/white bars depending on Dark/Light Mode.
  • Thermostat screen displaying in a larger font.

They may be converting the Android app from Java to Kotlin/Jetpack Compose UI … if this is true probably will see more UI issues in the short term but hopefully a more modern app interface in the long term.

Soon enough Claude will be writing the whole app.

I was going to try going back to an older version of the app from before the problem started.

But, on trying to install 3.18.0.918 (July 23, 2026), I get the warning that there is a “version conflict” and that I need to “first uninstall the installed one.”

What will I lose by doing this?
Will I have to re-do all my settings, e.g., detection zones, automations, and all that?
If so, that is not worth the effort.
I’d rather just wait for the fixed version to come out.
I can watch the large views on the PC Android emulator just fine, which is where I do my more serious viewing,

You’ll lose some preferences like notification sound/settings and stuff, but detection zones, automations, and cam settings should stay, those are stored on Wyze servers.

I’ve never reverted to an older version so I’ll let someone else reply.

But if you want to view the full landscape view on your phone it still works on the monitoring tab … you have to click the orientation icon to manually change to landscape … if it is the only camera on the page it will display in full o/w click the double arrow icon on the camera view to expand to full screen.

… and include the link to the Chinese DNS servers :joy:

I think that’s the least of my worries when people start letting AI code for them without thoroughly reviewing (or understanding) it after. With each new model that comes out it has been showing more and more tendencies to do malicious things.

Linux has placed a ton of scrutiny around community contributed content that was done with AI, which is a very smart move. Kernel and driver updates specifically are nearly flat out prohibited. I use a lot of open source software for various things and run an internet facing Linux server (though it is behind a VPN with a lot of protections) and have been seeing a lot of blind AI updates come through for many of those apps, which I won’t install.

AI should assist/suggest, not control.

Agreed. But unfortunately the Tech Companies are all looking at ways to improve the bottom line with more AI and less humans.

So my best course of action is to keep on the present bum version, and monitor the version news until the white bar problem is noted as fixed, and only then allow the update.

Up to you, shouldn’t need to reconfigure much after uninstalling and installing an old one, but there will be some work involved. Disable auto update until it is fixed if you do downgrade.

I’m seeing this issue on my OG-Tele, but no where near enough of an issue to want to do anything about it.

Today’s 3.22.0.973 (September 16, 2026) update fixed this problem.