GoPro Hero4 Black audio ticking with WiFi enabled

Got a GoPro Hero4 to record some video for YouTube. It's a great camera. Small, waterproof, great quality video, a ton of different mounting types.

The Hero4 I have has an odd issue where videos recorded with WiFi enabled have ticking sound throughout the recording. Googling for the issue turned up a ton of similar issues, some reported a year ago across a range of GoPro cameras. It was surprising to me that new models like the Hero4 would have the same issue.

Update: Received a replacement through Amazon, where I ordered it from, and it has the same issue. I had contacted GoPro but they won't do cross shipping, even if you offer to pay for the replacement. Without cross shipping it would have been a couple of weeks wait for the shipment there and back on a camera I've had for less than a week.

It seems like there might be something wrong with the design of these cameras and I'm surprised GoPro hasn't owned up to it. Its not a debilitating defect. WiFi does drain the battery at a pretty high rate. It is handy when previewing video and its certainly possible to forget to check if its off before recording. In any case I'll probably just try to make sure to keep WiFi off when recording, I'm not sure its worth the effort of returning it to GoPro if two new cameras have the same issue.

Comments

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...

Travelling on Spirit airlines out of Boston Logan airport? Here are some tips.

I attended CES 2017 in Las Vegas. Booking the trip late I ended up on Spirit airlines. It was both non-stop, making it six hours to Las Vegas from Boston, and affordable, less than $300 for a one way trip compared to around $700 with JetBlue. Here are some tips that might help you when travelling on Spirit from Boston Logan airport. Eat Spirit is located in the B-terminal, gates B-37 and 38, with its own TSA security checkpoint. While it does have restrooms and places to sit the food selection is limited to a single food stand. I'd recommend eating at the Legal C Bar (number 77 in the image below) prior to going through the terminal security checkpoint. The food and service there were great. Drink The water and other drinks are cheaper if you buy them at the food cart rather than on the flight. Seats The seats on Spirit don't recline. They do this to reduce weight, seat cost, seat maintenance costs, and so seats don't impact the free space of other passengers,...

Yocto recipe SRC_URI for a BitBucket / GitHub ssh git repository

This is a particularly geeky post but because Google searches didn't turn up any information I thought it would be helpful to document the issue and solution for others. I was writing Yocto recipes that pulled from BitBucket git repositories in ssh form and ran into several issues getting a SRC_URI that worked. GitHub uses the same syntax for their ssh repositories. A BitBucket / GitHub git url, in ssh form, looks like: < username >@bitbucket.org:< account name >/< repository name >.git a more concrete example for a git repository in one of my BitBucket accounts looks like: git@bitbucket.org:cmorgan/somerepository.git Yocto recipes can pull from git repositories by setting the SRC_URI variable appropriately. Unfortunately you can't just do: SRC_URI = "git@bitbucket.org:cmorgan/somerepository.git You'll get errors because the Yocto won't know what kind of url this is. You need to specify the protocol for Yocto to k...

Chris M.

Search This Blog