after rides that aren't actually very long, the device can be very hot. The device does not seem to have any issues operating in these conditions, however, it can be unpleasant for a user to handle it. I would like to look into figuring out how to reduce this heat. There might be software optimizations to be made. Perhaps changing the power source would improve how the device operates. Maybe it would be best to look into adding a heat sink and making that part of the standard hardware setup.

Here's what's going on

When I go for rides sometimes I realize that I need to know what time it is

Here's what should be going on

Wouldn't it be cool if Bodgecycle Computer had a clock function?

This is currently the biggest goal of this project. It might work, but I don't know. I need someone to test it.

Every once in a while when a user tries to upload their file to Strava they will discover that they have the worst of all possible things: poorly formatted data. This is because the metadata section hasn't been closed and the track segmant section hasn't been opened.

Add the following instruction(s):

1. How to add TinyGPS++
2. That actually turns out to be pretty much it.

One thing needs to be treated carefully is that this process was different on my computer (running arch linux) and on my girlfriend's computer (running linux mint)

Whenever the battery starts getting low, lots of files are created in quick succession, none of them valid. Ideally we would be able to monitor the battery level and stop recording when it starts getting dangerously low. This is planned for a version 1.0.1 release in the future.

I am logging data every second as well as polling the GPS module a lot to find out when there are enough satellites to start logging. This needs to be remedied so that the platform can be used longer and has more stable behavior.