location coordinates are reset to NaN before the listeners are updated. This can lead to situation, where the location coordinates are NaN outside of LocationHandler

eastern direction use the letter O for german "Osten"

When the own location is known the alarm radar view can still be used to zoom/move to center the own location

GPS signal detection seems to oscillate between states even if there are enough satellites in view

add something like a service manager which controls the status of the app service depending on the current background period setting.

when displaying historical data the apperance of strokes should not change with time

add something like a service manager which controls the status of the app service depending on the current background period setting.

Instead of entering the manual position manually using the map directly would be a nice way to set it.

sevice should be disabled when starting at boot time and after the application was closed if no background activity is selected.

disable the LocationHandler when there is no use for location data. E. g. when the alarm is not enabled when entering background operation.

LocationHandler should auto detect and disable location when all listeners are removed. (This should be done by using ListenerContainer)

Maybe switch to context menu as options menu is not opened in some cases

this is mainly for non european users who have to figure out to go to the menu to enable data for their area

I looked through the code and noticed that configureServiceMode()
is called upon every run of AppService, even when run in background.
Is it necessary to do that?

Requesting Alarms/Reconfiguring the LocationHandler uses some CPU time every time data is retrieved.

enable users to switch region and raster size more easy

Vibration alarm will be replaced by generic alarm which can be configured to comprise any of vibration, acoustic or maybe even optical signaling.

Vibration alarm: choose length of vibration or off
Acoustic alarm: choose audio signal and maybe volume
Optical alarm: implement later as it requires permission to use camera

add preference setting to control behavior as well

Time scale in alarm manager is off by a factor of thousand

seems not to be activated even if alarms are enabled and background period is set

Do not wait until next data update to determine the warn status after the current location is fixed.

Create a widget which contains the alarm view compass rose.

It should be possible to show an animation of lightning activity over time.

E. g over the last three hours in steps of 15 minutes. (All parameters fully configurable, of course)

In order to reduce the data transmission volume and to achieve a cleaner map view a minimum stroke count can be applied for the data requests.

Add scaled view to have a better experience on tablets.

The following handlers should be integrated in the service to enable independent operation:

• DataHandler
• AlertHandler
• LocationHandler

This should stabilize the background operation and ensure a background operation after reboot. Widget integration will be easier later.

use both server addresses and ports (7080/80) in all combinations

Minimize the app by pressing the back button and then open the app again:
Result is that the "Lightning-Count" and "time until refresh" is not shown at the top of the screen
and i'm not sure whether the data on the map is still updated or not.

Closing the app completly and reopening fixes the problem

I'm using the BO app V1.2 on an Samsung S4 with Android 4.4.2
After some time (hours or days - not reproduceable) the battery gets drained faster than normal - in the battery history you can than see, that the phone doesn't enter sleep mode anymore and the BO app is on first place of power consuming apps. After killing and restarting the app, everything is fine again.

Please check this issue.

Thanks.

This is broken since the Kotlin migration

separate data containers from functionality to allow for better testability and cleaner code