Huh, interesting. We've had both those things before, but I've not seen them happening together.

this looks relevant
08-13 07:56:04.726 -0300 8124 8124 E AndroidRuntime: FATAL EXCEPTION: main
08-13 07:56:04.726 -0300 8124 8124 E AndroidRuntime: Process: com.casticalabs.forecastie, PID: 8124
08-13 07:56:04.726 -0300 8124 8124 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.casticalabs.forecastie.widgets.ClassicTimeWidgetProvider: java.lang.StringIndexOutOfBoundsException: String index out of range: -2

particularly, "string index out of range"

I assume a number between, say 0 and 6 is expected for some input or other. for an unknown reason -2 is returned. we could put in some logic to force it to default to 0 if it is outside the allowed range, or even better find out why it is sometimes -2

The clock widget crashes when I try to place it on my screen too.

Looked in the code for this and it appears to be related to a missing hyphen "-" in certain date/time formats, someone else found this here #287 (comment)

#365 fixed this for TimeWidgetProvider.java, but not for ClassicTimeWidgetProvider.java which also has this problem