Android Hotfix version 3.8.6.723 - Released 11/7/2025

My Cam v4 and Cam Pan v3 cams running latest beta firmware take considerably longer to connect compared to same models running production firmware. Beta firmware cams are taking 5+ seconds to start streaming. Production firmware cams start streaming in 1-2 seconds. Not sure what the deal is there. But all cams are still going strong with no connection hangups and no errors thrown. Not claiming success just yet though. I’ll be “playing” with all of the cams over the course of the day/night and keep these streaming 24/7 through tomorrow. Keep in mind we’re not beta testing. This hotfix app version is a public release, i.e., done deal and out to the masses. Since we’re running the same viewing devices (S24U and A9+ and I’m also running an A8 and A7), I’m still wondering if your subscription difference is related to your issues. Either that or your network is not as robust as mine?

Good points but..

Yesterday for approx 12 hours I ran without incident with production software on the Cam v4’s and CP v3’s. During this time I would check load time of my 11 cam group. It was 20-22 seconds, same as it’s been for weeks/months. I call this my litmus test. Last night after you updated to the hotfix, I did the same and updated a Cam v4 and a CP V3 to the beta firmware. After 15 minutes or so I felt that the hotfix had cured the issue and I added another Cam v4 and CP v3. At first it seemed good but after 15 minutes or so I started seeing the Cam v4 multiple try issue. That’s when I posted I was calling it a day.

This morning I reverified the issues were still there and posted that the hotfix did not cure it.

Could it be my network? Anything is possible but I have rechecked all my load times and I’m seeing small differences with what your seeing. I see no difference in load time between beta and production firmware. I see 2-4 seconds. Repeatable. The fastest is the newer CP v4, 2 seconds (and it’s outside with chicken wire stucco in between). The slowest is my v2 doorbell at 4 seconds. The rest are in the 3 second range. I do have 3 WBCP’s and they are in the 9-11 second range (as expected). If your network is more robust then I’m speculating it’s minor. As I posted earlier I looked very closely at the router/extender settings especially related to 2.4. I found nothing.

Could it be the subscription?Anything is possible. My response would be why is it working flawlessly with production firmware but not with the beta.

This one is a pickle, requiring a lot more time and brain power. I’m going to stand by my statement - - there is a gremlin.

BTW, I’m not going to change the cams that I updated last night. That way if Wyze or someone comes up with and idea or workaround it can be easily tested. I’m not severely impacted–it just takes some extra time, being retired, of which I have plenty of😄

2 Likes

You sound a lot like me. :rofl: And now I’m having occasional “Loading Live Stream” issues on random cams including Cam v3 and Cam v3 Pro. I’m going to ignore for a good while. It’s giving me a headache. :pensive_face:

1 Like

My sentiments exactly. Let’s take the rest of the day off.

Maybe a fresh team can take over.

2 Likes

I had to jump back into it.

You observed that the hot fix seemed to slow down your load times. I did not see this but I decided to look at the a9+ tablet. It was basically useless. On the s24 ultra my 11 cam group would load in ~22 seconds. On the a9+ the same group took 45 seconds. I had always attributed this to big differences in cpu horsepower and wifi vs wifi 6. Now it took minutes–if it loaded at all.

This spooked me as since the hot fix was quasi PR, I would be stuck with a useless tablet for the foreseeable future. Decided to try a few things.

I made a new group for just the cams I had updated to beta. There were 4 cams in that group. I expected doing this would clean up the big group, the house cams, as the beta cams would not be streaming live view. Was I mistaken. Both groups exhibited the v4 V3 problems we’ve been seeing. This would imply that the problems are created whether in live view or working in the background processing events. This made me remember your assertion that it could be the pro subscription, the only dicernable difference we’ve identified. I have no way of proving or disproving this (maybe seeing if I can remove or change the subscription. But I’m not going there–yet).

At this point I just wanted to prove if the hot fix was creating more problems–so out came the flash kit.

Since the v4 seemed to be a bigger issue I decided to flash both of them back to PR. I turned off the CP V3 ‘s, hoping this would keep them from processing in the background (not sure if this helped).

After clearing caches the results were worth the effort. My 11 cam group came up in ~25 seconds. I banged on it for about 10 minutes and had no repeats of the big issue. Only what seemed like a small slowdown.

I went ahead and reflashed the CP v3’s back to PR and continued testing.

Bottom line

I’m running the hotfix on 3.8.6 723

The CP v3’s are on PR 4800

The Cam v4’s are on PR 3415

There is a small slowdown with the hot fix. My a9+ tablet is operational. My group takes close to a minute to load. The s24 ultra may be 2 or 3 seconds slower. Instead of 22 seconds, maybe 25 seconds. In the past two hours I have not seen any spurious problems We’ve both seen unexplainable problems and hopefully those are history.

I know you were concerned that the hotfix would go to the masses. I’m less concerned after getting things back to PR.

Whew

Edit: There is still a nasty Cam v4 bug and lessor CP v3 bug.

1 Like

Are you concerned about what happens when the current beta firmware goes PR?

If you think performance is bad on an A9+, you should see what it’s like on an A7. :grimacing:

I still have some playing around to do, but I probably won’t get to it until Tuesday. I want to look at LAN traffic to see if any of the beta firmware cams are running wild. I also want to play with hardware decoder settings. When that setting was applicable at the app level and persistent to viewing device, I had it turned on for all of my flagship phones and off for all of my tablets. It worked well that way and horrible the other way around. Someone decided to move that setting to the cam level and it’s also persistent at the cam level per account, which means you can no longer set viewing of one cam one way for a phone and the other way for a tablet.

The tablet is usable.

This cannot go PR. We’ve proven there is a problem especially with the v4’s. The hotfix did not fix that.

Since we don’t know what the hotfix did we can only go by what we’re seeing.

Interesting u bring up the encoder. I did try it on the s24, all 7 suspect cams, but did not try it on the tablet.

1 Like

You know me and I’m glad to publicly post this that despite being a maven we are not selected for special stuff in this manner in that I usually waiting until the end until the updates are available for me. Im not seeing it yet.

1 Like

I’ve given pup on WYSE. your firmware just gets worse and worse. Two cameras usless now and your people can only say buy more. Sorry not falling for that.

1 Like

I am still on 3.8.5 (722)
Still dont see this hotfix on Google…
Has it been pulled?