Ignore RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground() with ACRA
There seems to be a bug on Android preventing Services to start because they fail to do so fast enough in some rare occasions. Since WaveUp normally works short after that. The reporters say that they've sent the crash report because the saw the notification, but the otherwise WaveUp works normally. This should be safe to ignore.
We could probably also do this with the Exception referenced in #125 although that's not as common as this one.
It would be nice to tell ACRA to silently ignore these Exceptions.