Recording period shorter than programmed

I have installed version 1.2.5. The app will not recognise local time. It registers 1969 when I select local time. I have installed new batteries in the AudioMoth, although I did not need to. I have rebooted my computer (Windows 10). I did not have this issue with 1.2.2. I did not have any recordings when I deployed it for 12 hours last night (33 degrees F this morning. Older batteries at 4.0 V.) That has never happened but may be unrelated and perhaps I did not throw the switch all the way to custom.. Nevertheless, I just test recorded in default mode and it recorded fine but the date on four files was screwy. What is going on? Can I get back to the older configuration app? After this I flashed the unit and it now contains firmware version 1.3.0. I then deleted the configuration app from the computer and loaded it fresh. It still will not recognise the correct local time. I have some time constraints on what I am doing. This problem does not help. SOLUTION: Finally, I added the new version of the app to the Windows Defender firewall, and that appears to have resolved my issue. Interestingly, prior to this solution, when I reinstalled the app it would put the icon in the tray, but it would not automatically create a shortcut. Now it does, and all is well.

Hi, open and save configuration worked well before updating for last firmware. But, it seems not to work anymore ? Inoperative function in the menu. Any ideas ? Thanks.

Currently in the field where I deployed two Audiomoths, that were tied on a tree (next to each other). Each recorder was tested with different batteries to test how long they last (Duracell and Eveready). I am currently using a San Disk Extreme - UHS 3 as recommended and the latest firmware - 1.3.0. After 3 days of recording, when I retrieved the memory cards, I see a ton of white lines at high frequencies in almost all of the recordings. Why is this happening? What's the solution?