The Android 13 update came down to my Pixel 4a/5g this afternoon.
For some reason now I cannot play back footage from my V3 cameras (off the SDcard).
Also, when I select a V3 camera from the camera list, the image freezes.
When they are in the multi-camera view they work fine.
The V2 cameras do not seem to be affected by the update.
Events from Cam+ seem to work fine.
My Android Wyze app is at version 2.33.1 (162).
I know this new Android version is coming down to the Pixel 4 on up, so this may be going to cause problems to others soon.
Thanks
1 Like
I did the clear cache and logoff/logon.
This did not fix the V3 camera problem on Android 13.
I am not ready to re-install the app just yet though!
All this was working before the update to Android 13.
I am going to call it a night for now, maybe mess with it tomorrow morning!
Thanks very much for the help!
I just updated my Pixel 5 to Android 13 and tested this and I am able to view playback footage from my V3 SD cards okay.
I also loaded up a virtual Pixel 4 on Android 13 and it works fine too (Iāve been using Android 13 on a virtual Pixel 4 for months now without issue, but I just tried again today and itās still working well).
I guess try rebooting the camera. If that doesnāt work, try swapping the SD card and see if that makes a difference. Otherwise, contact support and theyāll see what they can figure out. I donāt think it is related to Android 13 specifically, I think it was just a bad coincidence. Often power-cycling the camera will fix an issue like this.
2 Likes
I turned off/on several of the V3 cameras, and that did not fix the issue.
I was able to go into settings and view the SDcard status on the V3 cameras, and all showed fine.
When I returned to the live video feed from the settings, live view was working fine (not frozen).
Viewing the contents from the SDcard works too when I use this method.
If I go directly from multi-camera view to single live camera view, the image is frozen.
If I go from multi-camera view to single live camera view, then settings, then back to view, it works fine!
This is a good work-around for me.
1 Like
Carverofchoice and Rulwiz,
Thanks for the tips!
I decided to see if my spouseās phone was having the same problem, and it was NOT.
She has the exact same phone I have (Pixel 4a/5g).
I painstakingly went through all the Developer Option settings. I knew I had adjusted several of these trying to get the Wyze VDB (v1) to work in the past, but all were the same.
I then went into her Wyze App settings and compared them to mine.
I had turned ON āEnable Hardware Decoderā on my settings in the Wyze App trying to fix the VDB.
Once I turned āEnable Hardware Decoderā off, it started working properly again!
You get to this setting by clicking āAccountā then āApp Settingsā.
Thanks again!
6 Likes
Interesting. Thanks for the follow up and clear explanations. This will be a helpful reference if someone else is having a similar issue in the future.
1 Like
That was a pretty bizarre problem. It had to be the Android 13 update that caused that switch in the Wyze App settings (Enable Hardware Decoder) to start causing video playback trouble on the V3 cameras. I used the playback ALL weekend on Android 12 and had zero problems. It just happened Monday Afternoon when I updated to Android 13. Hopefully they will get the Video Doorbell (V1) firmware working correctly soon!
Yeah, I wonder if it changed how hardware decoding functions now or something. I might do some testing when I get some spare time.
I know theyāre working on the VBD firmware fixesā¦they just want to stabilize it as much as possible before going public.
Additional noteā¦ I have been using the Android 13 beta for a couple months and it has not interrupted anything Wyze related. Android 13 is pretty boring IMO. They shouldāve called it Android 12.5.
-Earl
Yeah, the average person wonāt notice much difference at all. Most of the important changes are how things function behind the scenes. Still important, but it seems like it didnāt need to be a ānew OSā version for thatā¦shouldāve just a decimal incrementā¦BUT I think they partially like to do new OSās because it looks like progress and like phones were supported through more OSās, etc. 
Totally agreeā¦ I think they have tightened security, notifications, and made it much easier to see application permissions. Which is long overdue in regards to securing the Google OS. And, as a computer guy, I love to seeā¦ but, Iām also a tech nerd and wanted something to play with. So definitely a 12.5 but they have to call it 13 becauseā¦ capitalism.
Apple people always get new toys in their OS upgradesā¦ Android people get application permissions. ha.
2 Likes
Iām on IOS 16 public beta, and I get lots of cool stuff, such as a wallpaper that automatically tucks the clock behind the subject.
Also the ability to hold on any image and auto cut out the subject.
The fix they put in to block the animation on app close was very nice!
I block all animations using developer mode, but the app close animation snuck into an android 12 update several months ago. There was no way to block it!
It is now gone, and the phone seems a little more responsive.
One of my favorite additions to Android 12 was the ability to disable the MIC and Camera access from the pull down menu.
Anyone upgraded a Pixel 6 pro to Android 13?
I just got the update notice on my Pixel 6 pro, but I think I will wait due to Wyze Appā¦
Waiting to hear from another Wyze user thier experience after upgrading to Android 13 with the Wyze App.
@spamoni upgraded his Pixel 6 (and Pixel 5) to Android 13 and I upgraded my Pixel 5. Pretty good so far.
Though my Amazfit band is doing weird random alarms throughout the day that I canāt find or turn off anywhere. I think thatās unrelated, but it started around the same time I upgraded to Android 13 so I canāt be totally sureā¦it may be the fault of one of the 3rd party apps that connect to it tooā¦but I canāt find any alarms on them doing itā¦ Iām about ready to delete and set it up from scratch again or consider buying a newer one now. Again, I donāt think itās related, but it could be.
2 Likes
As @carverofchoice indicated, I have updated my Pixel 6 to Android 13 and I am not experiencing any issues. Matter of fact I am quite happy so far. I did install it on my Pixel 5 first as a test to see what the impact could be.
I am currently running the Beta App 2.34.0.b72.
2 Likes
I am using a pixel 6 w/ android 13 and several problems have popped up with my wyze hardware. The first problem I now have is that when viewing any of my v3 cameras and video doorbell there is no audio. The audio works fine with the recordings just not live. My next issue is that my wyze headphones are no longer an audio device. They are listed only as phone but no linger work with music and in all actuality, I have not attempted to make a call with them. However, I did try to delete my headphones and reconnect them and now the app can not find them. The only hardware that I am not having any issues with (so far) is my v1 cameras but I have not yet attempted to try out my robot vacuum yet but I will give an update when I do. So far android 13 does not play nicely with wyze hardware but I will keep testing things and try to find workarounds since wyze has been notoriously bad at fixing issues.
This isnāt because of Android 13. There is a known bug that causes this with beta firmware currently. You can flash back to a different firmware to fix it or wait for the fix.
I just barely used mine with Android 13 and they were working fine. I would contact support and go through the troubleshooting to fix this. They might have you set them back up from scratch. Thatās what I would try. Itās possible that Android unpaired them or changed Bluetooth autoconnect settings on you or something. Should be an easy fix.
1 Like
I have already set them up from scratch and now the app canāt find them. Bluetooth pairing without the app finds them but wonāt connect. I am going to uninstall the app as my next step but honestly at this point I am not expecting that to do anything since deleting the headphones from the app and having androidās Bluetooth connection āforgetā them only made things worse as they no longer connect at all.