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

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was

Memory efficient queuing of variable length elements

In embedded environments memory can be a critical driver of the design of data structures and containers. Computing resources have been expanding steadily each year but there are still a wide range of systems with far less than a megabyte of memory. On systems with tens of kilobytes of memory, structures are often designed to be compact to maximize data density. Rather than splurging on memory aligned elements that would be faster for the processor to access, a developer will typically use types with minimal sizes based on the known range of values that the element is intending to hold. Fixed sized buffers At my day job a fixed size pool of messages was implemented to hold message data. While this achieved one design goal of using statically allocated buffers, avoiding dynamic allocations that might fail at runtime, it isn't efficient if there is a wide range of message sizes. It isn't efficient because each message uses a message buffer. With small message sizes the buff

Chris M.

Search This Blog