I already mentioned that it was available for that app version, before it was pulled. Other posters have them working, too. Silently pulled. Does that imply that there was an incompatibility? Wyze would have been all over the place trying to justify why it was pulled. But instead, crickets.
Android version 9. The newer phone is version 14. Both phones are 64-bits. If they are limiting the pan cam V4 to Android 14, I don’t see it.
Android 9 is many years old and way out of support. It is certainly possible they saw issues with it and have now marked the software as requiring a minimum/supported version of Android.
I would ask in the Panv4 release thread or maybe the release thread for the latest app version to see if a new requirement has been added.
Then explain why it was available earlier. And not now. The hardware and software didn’t change.
You already did
And I made a guess as to why
If you want an official explanation, go into the release threads and tag some wyze folks, see if you get an answer.
What did change?
And the “incompatibility” guess does not fit, became it was working before.
On yours. Maybe others had problems so they pulled it and added a minimum OS version. Again, ask Wyze.
If it was working fine, why did you downgrade?
I did not downgrade. I repeat, there was no hardware/software change for the old phone.
Let me summarize this, using a timeline:
• 2nd day of release, people added the pan cam V4 to their Wyze app v3.6.7(694). Still buggy, but at least, they were able to test it. No mention of incompatibilities.
• 3rd day, people were reporting that their pan V4s disappeared from their apps.
• I got mine, but that time, it only worked on my new phone. I was able to replicate the bugs. My old phone doesn’t see it, and says, my app is up-to-date, even though I knew that there’s a new version. I assumed it was just a slow release.
• The next day, I got the message from Google Play that the new app version is incompatible with my old phone.
It probably was a slow release, and it probably is not compatible with Android 9, hence going from “up to date” to “not compatible”.
Obviously there was something that changed with the Panv4 or with the app where they had to update something, and it now requires the latest app. All I can say (again) is ask in the release threads and see, but seems safe to say the newest app is not compatible with your phone or Android version. Maybe they’ll resolve that and future versions will be, or maybe not. I wouldn’t hold my breath given how old it is.
I don’t have a problem if it’s indeed incompatible. But why was it not stated anywhere? Unlike the v2.50 version. Which leads me to believe the “incompatibility” isn’t real.
From what I recall, the only way we found out that 3.x would not work on 32 bit phones was through discussions in the forum here. I don’t recall anything “official” on their site etc.
I don’t have an answer for you. Wait it out and see if a new version of the app once again is compatible with your phone, or ask Wyze if there is a new limitation. Not really any other options.
The big difference is that with v2.50, nobody was able to install a later version on a 32-bit Android and then was “recalled”.
Who says that happened? It was never available for your phone. Others being able to install it on their phones is unrelated, different phones, different OS, etc.
Has anyone reported installing the latest on a phone, then for some reason uninstalling it and not being able to reinstall it?
Apple has been supporting the codec on iOS, MacOS and TVOS for as long as I remember. I might be wrong, but I think they were one of the pioneers of it way, way back.
To be clear, I believe that I had Cam Pan v4 visible (as in available to add to the app by navigating to ➜ Device ➜ Cameras ➜ Pan and Tilt Cameras) on Android app version 3.6.6.683 the day after the product announcement, and that’s what I was trying to report in the announcement topic. My observations in the past have been that Wyze tends to drop a new app version roughly coincident with a new product launch so that the latest app has the necessary components (i.e., plugins) to support the new products. Since the new app release lagged by a few days, I was speculating that maybe Wyze had temporarily enabled compatibility (whatever they have to do on the server side, since app features seem to be so tightly integrated with the back end) for the new device with slightly older app versions until the new app was released.
When the app was updated the following day, I installed that (3.7.0.695) on a phone running Android 10 and could see Cam Pan v4 there.[1] My phone that still has app version 3.6.6.683 (Android 13) does not show Cam Pan v4.
I think this is good advice, particularly since this discussion has strayed so far away from @barry2’s original topic, and the announcement topic for the latest app version seems like a more relevant place for these kinds of questions. Since those topics are actually initiated by Wyze employees, that might be a better place to get visibility and potentially a more direct response.
That has again been updated to 3.7.5.697 and is still seeing Cam Pan v4. ↩︎
Looks like they didn’t manage to get in on the patent/licensing game (but Google and several others did). But yes from what I recall the first time I ever ran into it was on someone’s iPhone from what I recall. I think someone sent me a picture or video that I had to install the (then free) codecs on Windows.
FWIW, I was able to change the user-agent string in both Microsoft Edge (tried on Linux and Windows) and Opera (tried on Linux) to enable Cam Pan v4 streaming in those browsers:
Firefox is a no-go, but it’s not Chromium based. I tried using User Agent Switcher and Manager to spoof the user-agent string in Firefox, but the browser itself is just too different and won’t work with this Cam, at least as far as I can tell.
I refuse to use Chrome, same for Edge. If I can’t use Firefox, then screw it.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.