@Todi: you can change the type of trigger by touching its marker on the map. A dialogue that allows you to change the trigger type appears. The default type is "Toggle" (blue marker). Camera recording is turned ON if not recording and OFF if recording. The reasoning is that if there's a particular section of road that you wish to record, you set the toggles at both end of the section and the recording is turned on once you've entered the section and turned off after you've left it, regardless of the direction from which you enter the section.
But you can change the type of trigger into "Start" (green marker, always starts recording) and "Stop" (red marker, always stops recording). There's also the option to "Restart" (orange marker) that you could use on a track to make one video per lap. And for more fine-grained control, you can set any trigger to activate only when it's passed in a certain direction.
Note that all of this is also explained in the context-sensitive help for the Triggers Map screen and the Trigger Properties screen. Each screen has its own help, accessible via menu (the three dots at the top-right of the screen).
As to why it doesn't work, I'd need more information. I have only tested the software on two Android devices (HTC One Mini and Nexus 10) with the GoPro Hero3+ Black edition and it has worked perfectly in both combinations. It is possible that other combinations somehow don't work.
Could you please make the following checks:
- Turn on the manual camera control: use menu, select "Settings", scroll down until you see "Manual camera control" and check the checkbox.
- Turn off the "Synchronise camera time" on the same settings screen (it could perhaps cause problems).
- Turn off the "Conserve camera power".
- On the main screen see if the "Power" and "Record" buttons do what they should do.
If so, the communication between the app and camera works as it should. You might want to turn the "Synchronise camera time" and/or "Conserve camera power" back on and test the Power and Record buttons again.
If everything works, then it's possible that there might be some problems with the acquisition of GPS data. But from the screenshot I see that the blue dot signifying "My Position" is on the map (near the Greenbelt Park), so apparently the location information is being acquired.
Perhaps you don't have the location mode set to use the GPS data, instead it may just use the WiFi and mobile network tower locations for an approximate location. For that you'd have to check the manual for your device, since this seems to be highly Android version and device dependent.
In the new version, there's an indicator on the main screen (just to the right of the "Location/Speed" radio buttons) that indicates the state of GPS data. Once the indicator turns green, the location should be good enough. If you select the speed mode, it should also display the current speed of the device. If the indicator stays red, there's almost certainly something wrong with the device's location settings.
There are two things you could try. First increase the trigger radius (in the Settings menu) to a large number, e.g., 100 metres. If that causes the app to start working properly, the location accuracy might be low. However, looking at the Google Earth map of the trigger locations, that seems unlikely.
You could also try the speed trigger - instead of location the recording is turned on above a certain speed and off below that speed (after some delay). By default the speed it's 5m/s, around 11mph. You could use the Settings menu to set it to 1m/s, which is 2.2mph, a slow walking pace. So the camera should start recording as soon as you start walking and stop 5 seconds after you stop walking (this is also configurable in the Settings menu).
If after all this you still cannot get the camera to turn on, there's apparently some bug in the software or you happen to have a camera that somehow works differently to the one I have. But please do the tests I've described and report back, so that I can have some clues where to look and isolate the problem.
And it everything else fails, I will add some logging code into the application to write a text file containing debug information.