Would like to purchase the new version of b1w, how can i tell who and if i am getting it with the rtc battery ?

lennyk

New Member
Joined
Jul 31, 2018
Messages
3
Reaction score
0
Country
United States
Would like to purchase the new version of b1w, how can i tell who and if i am getting it with the rtc battery ?
 

estore009

Well-Known Member
Retailer
Joined
Nov 25, 2013
Messages
2,594
Reaction score
1,251
Location
Shenzhen
Country
China
Dash Cam
B1W/B2W/B2K/B4K/DV688/DV988/B1M/B2M
You can buy it on amazon. It comes with an RTC battery!
 

jdct

Active Member
Joined
Jul 25, 2018
Messages
201
Reaction score
135
Country
United States
All my B1W's were manufactured before the real time clock battery was added to the unit, and I did not even know that the B1W had been updated with one back in 2019 until seeing this post. I was also delighted to find that BlueSkySea added some logic to the V20200707 firmware in order to work around the file naming/overwriting issues that can occur when the clock resets back to the default time after the capacitors completely discharge in a few days of being powered off. For my use, I don't particularly care what the files are named, or what time is set on the dashcam, because any dashcam without GPS to set time will always be wrong in some way. When necessary, I can establish precise time for recordings from my GPS-enabled unit, and synchronize all individual videos to a single prior shared reference point. But losing video files, or even having the potential to lose video files is simply unacceptable.

That BlueSkySea added this file naming enhancement functionality to the B1W simply to help their dashcam owners avoid losing necessary video files in such cases -- for units which were already sold long ago -- shows their dedication to customer service, and I greatly appreciate it. I have had so many various issues with dashcams from different manufacturers that I actually added a timer circuit into my dashcam power wiring, which turns on all my dashcams for 2 minutes every 24 hours, simply in order to refresh the charge in capacitors all around, to help avoid various issues like these.

Maybe it's time that I give that new 4K BlueSkySea B4K dashcam a look for the most important front-facing position in my car...
 

sdl87

New Member
Joined
Jun 8, 2018
Messages
21
Reaction score
13
Country
United States
All my B1W's were manufactured before the real time clock battery was added to the unit, and I did not even know that the B1W had been updated with one back in 2019 until seeing this post. I was also delighted to find that BlueSkySea added some logic to the V20200707 firmware in order to work around the file naming/overwriting issues that can occur when the clock resets back to the default time after the capacitors completely discharge in a few days of being powered off. For my use, I don't particularly care what the files are named, or what time is set on the dashcam, because any dashcam without GPS to set time will always be wrong in some way. When necessary, I can establish precise time for recordings from my GPS-enabled unit, and synchronize all individual videos to a single prior shared reference point. But losing video files, or even having the potential to lose video files is simply unacceptable.

That BlueSkySea added this file naming enhancement functionality to the B1W simply to help their dashcam owners avoid losing necessary video files in such cases -- for units which were already sold long ago -- shows their dedication to customer service, and I greatly appreciate it. I have had so many various issues with dashcams from different manufacturers that I actually added a timer circuit into my dashcam power wiring, which turns on all my dashcams for 2 minutes every 24 hours, simply in order to refresh the charge in capacitors all around, to help avoid various issues like these.

Maybe it's time that I give that new 4K BlueSkySea B4K dashcam a look for the most important front-facing position in my car...
What makes you say that V20200707 has the workaround for the RTC losing time?

My understanding is that V20201117 has that fix, but shouldn't be used because it's buggy.

See here:

And the discussion here:

I think their inability to actually publish a stable fix for this issue shows their lack of dedication to customer service. The issue has been around for years, and the only fix they produced is buggy beta firmware that they don't recommend people use.
 
Top