I am writing to ask why Android hardware decoding was removed? Was it intentional? If so, I will be returning my 12 cameras which are now for all practical purposes unusable. Don’t think I will pay extra for that. I won’t. Put it back WYZE.
@WyzeRoy Does this mean that:
The Wyze app is now checking the operating system active on your phone/tablet for the hardware decoder setting designated (globally) there?
@WyzeRoy I’m afraid that new decoder suck.
Yes, it does suck. It is unusably slow. If this is how it worked when I bought my first camera, it would have been my last and I would have returned it.
It was perfect before. No lag at all. Now there is lots of lag. Also, in the past, I have had problems with the app bombing out after switching between viewing a few different cameras. It now appears to be even more unstable.
Add me to the list of people who are annoyed at the lack of the enable hardware encoding option as the cameras are basically unusable now.
The video is delayed by about 24 seconds and it looks like it is in slow motion but it worked fine in prior versions that had the hardware encoding option.
If the app is now auto-detecting it from my Andriod OS, either it is doing it wrong or I need to change something in my OS settings. If that is the case, please let me know what to change.
Same issues with me. I can see the recorded events but live feed is useless. I need that decoder put back on there.
Yes, that’s what I’m seeing. Probably a good 20 second delay. At first I thought maybe my wireless network was acting up or the server was slow or something. Then, I went looking for the hardware decoding setting and couldn’t find it and realized that that was it. Wyze can put all the AI in the world in the system and it doesn’t make a difference if you can’t play the videos.
I found a link somewhere on these forums for reverting back to the previous version. I deleted app and reinstalled older version. Now my live feeds are working again.
I will proxy for Wyze and its trusted gearheads in answering the topic’s title question:
Why was Android hardware decoding removed?
In order to assess customer need for it by monitoring for negative feedback.
- The mod/maven/regular/staff vacuum hereon
- The relatively few complaints posted so far
- The absence of complaints on wyze reddit forum
I am anticipating that our goose is cooked on this one.
I suspect it may be subtly suggested to those of us with older devices (one likely culprit) that it’s time to upgrade them to something more recent and spunky.
If you’re already running recent monster gear, they’ll be quite interested and will investigate further via support ticket.
Active minds in a vacuum will speculate. It’s a law of nature.
Interesting. In post 5 you explain why hardware encoding was removed (they changed programming libraries), and then you write the post above (it was removed to assess customer need for it by monitoring negative feedback).
Changing programming libraries is the correct answer. An official post by a Wyze employee. Unfortunately, this also means replacing the functionality may not be possible.
Sorry to add to this issue, but I’m seeing a 12 to 15 second delay on my CamPans as well. At first I thought it was either my phone or my network. For example, when I pan the camera, there’s a noticeable delay. The delay was so much that I thought someone else was controlling the camera. This isn’t very helpful if I need to manually watch something - it just won’t keep up. Thanks for any help in resolving!
I have this same issue now. Makes the cameras useless. Where did the Hardware decoder option go? It’s now longer in the app settings.
Hi Newshound, I posted WyzeGwendolyn’s comment from another thread. I don’t fully understand what it means or its implications. So I guessed. Can you explain what changing programming libraries means and why they might do it?
You’ll notice I first posted WyzeRoy’s comment without fully understanding its meaning or implications. So I asked for clarification.
To respond to your earlier comment, yes, I do think you all know more, both technically and wyze-org’ly. There are a lot of IT pros (both active and retired) and many true fanatics in this community. I’m barely within sniffing distance of any of that.
I appreciate your efforts in gathering the answers you did. Your 2 posts is how I found out those two answers were available, so I thank you for that. I have tagged both of the employees in hopes of getting a clearer answer (as you did). Hopefully they will chime in.
Of course it is late in the afternoon on a Friday there now, so we may have to wait a bit.
Like they deserve time off. Slackers.
No rest for the wicked, I suppose!
I’ve been sending this feedback in to the team and we’re not ignoring it. No, this change was not made to assess customer need for it by monitoring negative feedback. While this was not done as well as it could have been, we weren’t doing it just to see if it’s still needed. We have better options (like actually asking our community) if that is what we’re aiming for. This was a change because of switching libraries.
If you are negatively impacted by this, please contact our support team. I’m collecting data about impact and the symptoms for the team.
The lag makes the camera almost useless to me. If it’s not fixed I won’t be buying any more Wyze Cams or recommending them to anyone.
Could I ask what device and Android version you have?