Hi everyone, we have a hotfix going out for the Android Wyze app with a few bug fixes. The new version is 3.8.6.723.
Any idea what was fixed. I’m just recovering from the recent v4 beta and I’m thinking there may still be an issue with the CP v3. If the hot fix is related to either of those cameras then I’ll install it. Otherwise I’m going to hold off. I’m a bit beta shy after the events of this last couple of weeks. Thanks in advance.
2 Likes
Has anyone seen this hotfix update yet? Still waiting…
1 Like
I have not, but I also haven’t yet seen the September 2025 production firmware update for Video Doorbell v2. I don’t know if that one had problems or if it’s just an abnormally slow roll-out (which apparently has happened before).
When “hotfix” is part of the announcement, I expect general availability to be much sooner than the normal phased deployments, but I don’t know if Wyze is using that term in that manner. 
1 Like
While I expect a hot fix won’t be intentionally phased, they are still subject to Apple and Google’s review procedures. Google in particular routinely holds up release of a new app for 7 to 10 days especially so that they can make sure there are no loopholes for purchasing subscriptions except directly through them. It’s pretty common for a release announcement to take up to a week before Google approves it.
2 Likes
Oh, yeah, I get that. I just know that Wyze has said in the past that they often don’t release an update to all users at once when the update is announced. I don’t know what their process is for doing something like that, but if they know that they’re releasing something that addresses specific bugs and calling that release a “hotfix”, then I wouldn’t expect them to use this same slow-roll process if the goal is to un-break something that’s affecting masses of users.
2 Likes
I just want to know what the “specific bugs” are that got fixed. 
2 Likes
Same. I’d really like to see more detail, and I’m wondering if any of those fixes address the UI issues that some Android issues have been reporting (unavailable Wyze app controls because they’re beneath or behind Android UI elements).
I realize that writing those kinds of notes takes time and effort, and it’s one of the things that I’ve appreciated about Discord for a long time. Here’s the beginning of their entry from a recent update:
My favorite part: “Bug fixes and performance improvements. Thank you for your time.”
2 Likes
Less effort than us trying to help forum users to no avail when there is no solution due to unacknowledged “bugs”.
2 Likes
Oh, that. Gwendolyn said they almost ALWAYS hold back at least a small number of users because it’s the only way they can cancel an update if it turns out to have a critical issue. I bet they do it with hot fixes too just in case. I have always seen that policy is different from a phased rollout though. I think of a phased rollout where they do multiple percentages over a few weeks. They usually do that with firmware. I think phased rollouts are fairly uncommon unless they pretty much know there is definitely going to be a percentage of people with issues that will be contacting support. The other version that they almost always do is what I would call a safety holdback cohort. I think that is only done for Android app releases and it is always done even if they believe everything is going to work right. Whereas, I think the phased rollouts are usually only done when they know there are going to Almost definitely be a percentage of issues and don’t want them all to flood support at the same time.
But, you could be right that maybe they don’t hold anything back for a hot fix at all. Or, maybe they still hold a small percentage back, but leave the hold back interval For a shorter time. Maybe if there are no negative reports within a few days they just push it out to the rest of the people that were held back for safety. That would make sense on a hotfix release.
At least that’s how I understood the 2 different kinds from what Gwendolyn said publicly in the past. 
But I definitely might have read between the lines and things could always change for sure.
To be honest though, I’m not sure they really need to do a safety hold back cohort any way. Worst case scenario, if a new app update turns out to have some problems, there is an easy way to cancel the update, just roll back to the previous app version, update the version number to higher than the most recently published app update, and submit the previous app version to be a newer version. Poof! The buggy app gets overwritten by the previous version that didn’t have those bugs. At least I assume it could work that way without needing to hold anybody back for any updates.
It just appeared in Google Play. I have “beta shy” so I’ll let others be first. 
4 Likes
I’ll be the Guinea Pig. 
So far so good. I can access and view cams. Will load it on a few other test phones and tablets, start up a bunch of live streams and let them run 24/7 while testing some Wyze non-cam products too:
I’ll concentrate on Cam v4 and Cam Pan v3 streams.
2 Likes
Loaded on some Android 12, 15 and 16 devices. Initial observations… cam streams initiate much faster. I can access all flavors of Wyze devices with no issues. Going to stream 12 cams simultaneously over 3 tablets concentrating on those running beta firmware and randomly dive into different parts of the app from a few phones.
Hmmm. Sounds encouraging. I’ll dip my toe into the water and install the hot fix and one each of the Cam v4’s and CP v3’s.
Small prayer and the flash kit is at the ready!
Thanks for being the guinea pig.
2 Likes
It’s been only 40 minutes, so it may be too early to tell, but it does appear that my beta Cam v4 and beta CPv3 issues are gone using this hotfix app. Hopefully you see the same.
2 Likes
I’m going to hold off my recommendation.
I added the hot fix, one each of the Cam v4 and CP v3. Stressed the group and individual cams and all seemed well.
Added one more of each cam. Over a period of 10 or so minutes the v4’s exhibited the problem.
Just to be sure I’m going to power cycle the network, and then call it a day.
1 Like
The hot fix did not fix the Cam v4 and CP v3 issues.
1 Like
You seeing authentication hangups and possibly 3005 or 3006 errors?
I may have one or two but mostly the multiple tries. The v4’s seem to have an issue about 2-3 times out of 10. The CP v3’s are much rarer, maybe 1 of 15 (these are seat of the pants estimates, not scientific).
I hate to add this to the mix but this morning my V3pro was acting up. And I’ve seen some 3005 errors, but even odder is the resolution indicator has been showing “auto”. To my knowledge that has only been implemented on the CP v4. This is totally out of character for the v3pro.
Edit: I’m going to monitor the v3pro. A power cycle appears to have fixed it.
1 Like