I am unable to duplicate this issue on any of my V2, V3, or OG-Tele cameras when I just tested this. Note that this is a function I use quite regularly, so I would likely have already noticed.
I am curious what camera you grabbed that screen capture from. Neither the V2 nor V3 shows that exact icon arrangement. If in portrait, the forward and back are below the image, and in portrait, you should have also seen the timeline. The OG is quite different.
Also, please don’t refer to “the latest update” - it can be ambiguous. Instead give actual version numbers. What is latest for you may not be the same as for someone else, or if may change five minutes after you post.
Phone: Moto Edge+ 5G UW (2022) running Android 13
App: 3.2.0 (580)
V2: 4.9.9.3006
V3: 4.36.13.0416
IOG-T: 1.0.80
It’s the lastest APP update
That has been released in the last day.
( of course its a rolling update, to reduced the load on the Wyze Servers so some users dont have the update yet)
App version 3.2.0(580)
Not sure if you are aware, but when someone says it the latest update, that tends to mean the most recely released update from Wyze. Software or Firmware releases dont change 5 seconds or 5 minutes later, Wyze tends to release them every few months.
Its the app, as this problem has never occured since the specific 30 sec Forward /Reverse feature was available.
I have been using Wyze cams for years.
All my cams are aways kept up to date with latest firmware.
I also use this feature Regualarly Daily
When something stops working after the most recent Wyze App release, 99% of the time it usually points to the New release App or Firmware.
As I initially posted it happens on ALL Cams v2/v3/OG’s
All cams/Wyze devices, always have the most recent version of firmware.
But it is recommended to state your actual firmware or app versions because that helps determine what branch, the beta app, or production app that your on. Those app branches have different app versions and when an issue is found on one or the other, there are different ways to report the bug. Also its recommended to state your actual app or firmware version because people search the forum, and searching app or firmware versions is one way to find same or similar problems. If you dont state that here, then it cant be grouped with potential other bugs from the same app or firmware version.
I dont (most people don’t) install Wyze Beta versions, or beta version anything.
The app testors can play with the beta’s, Beta apps always have bugs, and that is what beta testors are for.
Those who want constant app stability, don’t install beta versions.
Overall this is a “general forum”, not a “trouble ticket” submission, like the way many companies have a specific process for the end user to submit the hardware details & app build numbers when submitting a troulble ticket.
The post was to generally speak of the issue, and also see if there are other people experiencing it. Thats all…again most people that are not beta testors but keep the devices and apps up to date would understand what “the latest version” means.
Beta testors usually have their direct communicaton area or submission area, directly to the developers.
If I submitted a trouble ticket, all the app builds and firmware versions would be sumitted as vendors tend to require.
What happens if someone comes to the forum two months from now with the same issue and the app has been updated twice in that time? Will your definition of app being “up to date” hold water then?
If the user only disovers the same issue, 2 months later than my post, that means they dont use the app much.
And by the time they discover the issue, like you said, there will be 2 more updates released by that time
So they can just update to the latest App Build release,
which by your hypothetical example, would be 2 new app update releases AFTER my posted date/issue.
There are piles of users here who beta test either app versions, or product versions or some combination of both. And not everyone updates regularly even if they are not in the beta program.
The point being, specifying the version numbers involved IS relevant - at any time.
In regards to roles of a “Forum Admin”,
YES
A Good Forum Admin should also know the database the forum app runs on, and that includes keeping the database Optimized.
Optimizing a database, part of it, is cleaning up old useless data, defraging the database, tunning it, keeping it optmized so the forum sight does not go down, or the database it runs on, does not get corrupted over time. All databases must be kept optimized, there is some aspects of automation that can be setup to perform database optimization it, but overall, overall database administration have to keep up on the size, speed, and tunning a database, and this forum, as many others do, run on database applications.
It not just a matter of setting up a Forum,
and just keep letting it run for years, until it breaks
Thank you!
Yes, I came just to visit and post about the issue experienced with the lastest update, never thinking i would get somewhat piled on, just for my initial post, and then be told I am being selfish. because of the way I posted it.
So much for the issue at hand.
And I woke up today thinking today would be a great day
(There is still time left in the day !)