Quickly growing log files

thankssign

1 Like

You’re welcome! I’m told that we’ll aim for the fix in 2.15. Please keep in mind that the fix may be pushed to a future version if needed but please test the 2.15 app when it’s released and let me know how it goes. :slight_smile:

5 Likes

Will do. I appreciate the heads-up! :+1:

1 Like

Just fyi, my problem seemed to start with remotely connected outdoor cam. Remotely meaning wifi conected to outdoor cam located accross town.
I have had a ~15Gb txt file twice now. Also can’t seem to locate the file on Samsung SM-T290, Android version 10, without connecting to a pc.

Add me to the list of people who discovered this problem My log-iotc.txt file was about 5GB, and log_avapi was about 1.5GB
I’m on Wyze app version 2.15.11

Have been using app version 2.15.16 (beta), and can confirm that the log files are no longer being created on my Android phones or tablets. Edit: unless the files are being created somewhere else that I haven’t yet noticed. :wink:

On Android 10, Samsung T590
App 2.15.16
I just erased a log_avapi.txt that was 19.7GB.
I believe it was four or five weeks ago was the first time I noticed that file, and also the first time I erased it @ 12 or 13 gigs.
Today was my second time.
IDK if this will help, but found this month’s wifi data usage some 4x about its previous 3 months, to which those are usually 50 to 80GB.
With a week left in the monthly cycle, I’m just under 250GB.
@Mods or @WyzeGwendolyn <<- as you appear to be most active, could you shine a light as to both the purpose and usefulness of this insanely fast growing LOG FILE please??

Same here. I’ve deleted this log file 3 times in the past month.l, each time the file over 10GB in size.

I have two Samsung tablets running Android 7 and 9, and two Motorola phones running Android 10, all of which had the log files issue. As I mentioned several posts above, the log files have not reappeared on any of the devices since updating to the beta version of the app (2.15.16). I did fail to mention, however, that I also updated all my cameras to the latest beta (.213) at the same time. Perhaps this is the difference?

Just getting on the “me too” list. I thought my tablet was failing and I factory reset it. The only thing I use this tablet for is as a Wyze cam monitor, and Wyze is literally the only app I installed after this full reset.

It took about 3 days for it to entirely fill up the storage with a 24GB log file. Same as everyone else here who is reporting it.

Cameras and app are on latest version.

Y’all introduced a bug, please remove it.

2 Likes

Mine is 25gigs and takes over my phone making it unusable. I realize this camera is cheap, but don’t you have any pride? I wish I would have returned it while I had the chance.

Just letting you know that the problem still exists under production v.2.15.21 for Android.
.
.
—> Also… the latest Samsung user interface for Android 10 devices (phones and tablets) now includes a Trash Can for files. The trash can does not empty itself… you must manually empty it. If you delete a large file like log_iotc.txt, you must also empty your trash can after deletion or you will have recovered no additional space.

To get to the trash can, open Samsung’s “My Files” app > click on “Internal Storage” > click the 3 vertical dots in the upper-right corner > select “Trash” from the pulldown menu > click “Empty” in the upper-right corner > click “Empty Trash” on the confirmation pop-up.

2 Likes

Since updating the app to v2.15.21 (Android) I haven’t seen the log file grow much in the last few days - even after leaving the camera viewing for a few hours, the file is only 60 MB.

I’ve been cancelling all the prompts to update the firmware so my CamPlus V2 is still on 4.9.6.193

To me, it looks as though the App update has resolved the problem. But it doesn’t seem to have helped for Seapup so maybe it’s not yet fully resolved. I’ll report back if the log file gets big again.

Yeah I use an old phone to view it all the time and it fill up the 3GB every day. I checked my main phone recently and had over 40GB

Ok, I just had this bad experience as well. Just today one of googl’s intrusive app ( Gallery ) turned out to be a good thing. It alerted me of this outlandish sized over 6GB log file: log_iotc.txt. I had to googl it since I had no clue to what it may be. WTF. Wyze is reading and writing to a 6GB log file??! My setup:

  • Android 9
  • Wyze app 2.15.21

My experiences w/ this version of app I think bc it’s only been happening lately:

  • App wouldn’t launch or wouldn’t launch in reasonable amount of time. I waited a full minute.
  • App would crash
  • I had to stopped the app and relaunch
  • On launch it would display weird debugging like msgs “group-xx” etc
  • On launch it would show all of the devices broken out of Device Grouping

I’ve invested so much $$ with over 30 V2, 2 locks, 3 WCO that it’s hard to give it all up to find anew.

I JUST wish Wyze would put a bit more investment into quality instead of quantity of products!! So far it’s been as useful as my toddler’s electronic gadget.

v2.15.21 seems to solve the log problem, at least on my phone. Since you have v2.15.21, I wonder whether the 6 GB log file log_iotc.txt was created using the previous version. Try deleting that file, then view whether the file reappears. It should not. After my Wyze app was updated to v2.15.21, the log files no loner appear on my phone.

1 Like

Same. App 2.15.21 fixed it. The log files are still there but no longer growing. It’s easy to confirm - check the current size of the logs, watch a camera live feed for a few minutes, exit and check the log size.

Like Robert, I’ve been having strange app crashes lately where it completely freezes. Even the phone’s back or home buttons don’t work. I have to lock the phone and unlock it to free it up. I don’t know if it’s the app or if the phone is getting old. It has happened a few times in the last few weeks and only in the Wyze app. Nobody else has mentioned it so I’m assuming it’s just my phone.

It just got updated to 2.15.51 Unfortunately I didn’t keep tabs of when/where/what, but I was able to delete the log_iotc.txt.

  1. However, I forget where it was found. My mistake in original report, it’ was not the Googl’s Gallery but Go File app that found it and where I deleted it from. I think it was in the root of int memory? Nevertheless, got rid of it.
  2. App still occasionally crashes upon launch. No diff from 2.15.21 but does launch faster.
  3. 2.15.51 still shows every device then reduces the main view to grouped view… Wish it was cleaner, smoother more elegant than this less than polished look/feel.
  4. 2.15.51 although same as previous has same issue (digressing here) when scrubbing through the recording on the sdcard really really painful. Because one has to actually record from start to end time you want to save, one issue I keep running into is it records then at a certain point possibly trying to merge the vid file segmentation it keeps failing. Had to record the same section about 10x before I was able to save that segment.

[UPDATE] App froze at launch again. 2.15.51 now first time seeing android msg: Wyze isn’t responding x close app msg.

So I’m just finding this problem that was posted months ago but I don’t see any posts saying it’s fixed. Status?

The problem has been fixed for a while. Are you experiencing it now or did you just now find the files from when the problem existed?

1 Like