mathisdt / trackworktime Goto Github PK

Android app to track your work time via WiFi or location and categorize each recorded intervall by a predefined client/task and a free text.

Home Page: https://zephyrsoft.org/trackworktime

License: GNU General Public License v3.0

Java 100.00%

hacktoberfest android work-tracker working-time

trackworktime's Issues

data backup to SD card

TWT should have an option to enable copying the data to a SD card (customizable directory if possible). This should happen on every write so a suddenly defective phone won't make the data inaccessible.

Overview by day/week of time sums by task

This may not be a bug (unless not being able to find something is a bug) but there's something I can't find.

How do I find how much I've worked on each task summed for the day and week in app?

Case 1: I get to work on monday and have to fill out my time sheet adding the totals for each project for each day. Where do I go to see a days tasks and sums?
Case 2: I need to see if i correctly logged the time I spent earlier in the week on a certain project. I think I forgot to log the hour I spent reading a report on the train. Where do I go to see a days tasks and sums and make those changes?
Case 3: I logged 3 hours of admin today. On second thoughts I should have logged half of it to a specific project. Where do I go to see a days tasks and sums and make those changes?

The picture is of the in app report from ATimeTracker (which I am looking to migrate from because this report is also very tricky to use as a reference for making changes and correction.)

Location based tracking does not work

Using Android 8.0.0 on my OnePlus 3 phone, I have enabled Track by location, entered the latitude and longitude with a precision of 20 meters from the GPS, put a tolerance of 500 meters, and the tracking does no start automatically when I get to work. My home is about 2 km away so it should detect a change I think.

Wifi tracking not working with Android Pie

I recently upgraded my Samsung Galaxy S8 to Android Pie (9). Before that, Wifi tracking was working fine but now it just stopped. No events are logged at all. I already disabled battery optimization in the app's system settings (App Info - Optimize battery usage: Not optimized). Do you have some recommendation what could be done to enable this feature with the new Android version? Would be happy to provide you with more details.

add report: first login and last logout for each day

feature request (received by mail):

If I walk through my university I often leave the range of an WiFi AP and later coming again in to the range, this make TWT generate events every time . This is OK, but if I export the list at the end of the month, I have a lot of events every day. But I only need the first even (login) and the last one (logout). can you add a function in the reports to only count first login and last logout for the day?

create test suite

Create unit test suite, perhaps using Robolectric.
The package org.zephyrsoft.trackworktime.timer should be thoroughly tested, plus important parts of org.zephyrsoft.trackworktime.util.

fix remaining work time in notification

When the options "use flexi time 0:00 as target" and "countdown to 0:00 every day" are enabled, the notification sometimes displays incorrect finishing times. Especially high overtime amounts (more than one working day) could be the cause of the miscalculation, it seems that the displayed "possible finishing time" is from some days back. In case the flexi time is more than the rest for today it should display "now".

Method getFinishingTime of class TimerManager is likely to be wrong.

make settings easier to set up

when trying to use this app, I struggled a lot with (not so descriptive) error messages. you can re-try this by, instead showing agonizingly useless error messages, show dialog asking for additional information related to the feature - tracking by WiFi should show available WiFi SSIDs to pick, tracking by position should perhaps show dialog window with a world map rather than asking for gps coordinates, etc.

reset options on option value parsing errors

This is important especially on app start.

Request: View reports in-app

I'd like to see the results of the reports in the app before exporting it. Mostly I don't need to share the report with another app, I just want to see the information quickly.

Thanks

Notification permanently shown

I just updated to 1.0.3 and now I have a notification that is permanently shown and cannot be removed. It says "automatic clock-in by location and/or WiFi active". Regardless of whether I check the notification setting or not the notification does not go away. I believe the notification should not be shown if the setting is not checked.

make WiFi-based tracking work with Android 6.0 "Doze" / "App Standby"

The "Doze" feature which was introduced in Android 6.0 seems to confuse the WiFi-based tracking. When Doze is active, WiFi gets disabled and TWT clocks out. When WiFi is enabled again, TWT clocks in. This has to be corrected to ignore the "SSID unavailable" event when Doze is active.

Report: summing the times doesn't give the same results as the in app total

Reproduce

Have events over the previous week
Generate a report, eg.

sums-per-week-last-and-current-month
sums-per-week-last-and-current-year
(the clock was still running which might matters)

open it in a spreadsheet software
do the sum for one week of all tasks.
Details in my case:
4.1. use GNU Units eg. units --one-line --compact "5 hr + 22 min" hr -> 5.3666667
4.2. select all the cells to get the sum (LibreOffice)
Go to the relevant week in the app
Convert it's total in decimal
Observe that there is a difference

automatic backup

Automatically create a data backup every day.

multiple work places

support multiple work places for location-based tracking (latitude, longitude, tolerance)

fix IllegalArgumentException ("sum of a week may not be negative")

java.lang.IllegalArgumentException: sum of a week may not be negative
	at org.zephyrsoft.trackworktime.model.Week.setSum(Week.java:65)
	at org.zephyrsoft.trackworktime.timer.TimerManager.updateWeekSum(TimerManager.java:601)
	at org.zephyrsoft.trackworktime.timer.TimerManager.createEvent(TimerManager.java:584)
	at org.zephyrsoft.trackworktime.timer.TimerManager.createEvent(TimerManager.java:544)
	at org.zephyrsoft.trackworktime.timer.TimerManager.createEvent(TimerManager.java:528)
	at org.zephyrsoft.trackworktime.timer.TimerManager.startTracking(TimerManager.java:172)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.clockInAction(WorkTimeTrackerActivity.java:321)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.lambda$onCreate$3$WorkTimeTrackerActivity(WorkTimeTrackerActivity.java:218)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity$$Lambda$3.onClick(Unknown Source)
	at android.view.View.performClick(View.java:6205)
	at android.widget.TextView.performClick(TextView.java:11103)
	at android.view.View$PerformClick.run(View.java:23653)
	at android.os.Handler.handleCallback(Handler.java:751)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6682)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)

make start of week customizable

A user suggested to change the start and end days of the week. He said: "Our pay weeks go from Friday at 3am to Thursday at 3am, so to be able to track it that way would be really awesome."

WiFi based tracking keeps disconnecting

Using Android 8.0.0 on my OnePlus 3 phone, I have enabled Track by WiFi, entered SSID of my Workplace network, and the event log is full of IN/OUT events every couple of minutes, even though the SSID never loses signal.

IllegalArgumentException: Minute is not in the range 0..9999

java.lang.IllegalArgumentException: Minute is not in the range 0..9999
	at hirondelle.date4j.DateTimeInterval.checkRange(DateTimeInterval.java:118)
	at hirondelle.date4j.DateTimeInterval.plusOrMinus(DateTimeInterval.java:100)
	at hirondelle.date4j.DateTimeInterval.plus(DateTimeInterval.java:27)
	at hirondelle.date4j.DateTime.plus(DateTime.java:1046)
	at org.zephyrsoft.trackworktime.Basics.checkPersistentNotification(Basics.java:274)
	at org.zephyrsoft.trackworktime.Basics.safeCheckPersistentNotification(Basics.java:242)
	at org.zephyrsoft.trackworktime.Basics.periodicHook(Basics.java:198)
	at org.zephyrsoft.trackworktime.Watchdog.onReceive(Watchdog.java:34)
	at android.app.ActivityThread.handleReceiver(ActivityThread.java:3187)
	at android.app.ActivityThread.-wrap17(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1672)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6494)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

fix error looking up the WIFI_SERVICE

trackworktime/app/src/main/java/org/zephyrsoft/trackworktime/location/WifiTrackerService.java:50:
Error: The WIFI_SERVICE must be looked up on the Application context or memory will leak on
devices < Android N. Try changing  to .getApplicationContext()  [WifiManagerLeak]
  wifiTracker = new WifiTracker((WifiManager) getSystemService(Context.WIFI_SERVICE), basics.getTimerManager(),
                                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Explanation for issues of type "WifiManagerLeak":
   On versions prior to Android N (24), initializing the WifiManager via
   Context#getSystemService can cause a memory leak if the context is not the
   application context. Change context.getSystemService(...) to
   context.getApplicationContext().getSystemService(...).

database abstraction framework

Check if using Google's Room Persistence Library or greenDAO or ObjectBox (also see here) could make TWT easier to maintain.

use new permission model

The permissions ACCESS_COARSE_LOCATION and WRITE_EXTERNAL_STORAGE should be checked using the new permission model of Android 6.0+.

Request for new Report: Listing of data next to each other per day

I have a request for a new report. Is there a possibility to export the *.cvs in a way that the data in Excel are not under each other but next to each other per day? Something like that:

date / start of work / end of work / break time / working time /

Any help would be welcome.

Request: report for all times

At the moment reports exist for current and last time frames, but the most useful kind of report for me would be all times for one task.

Cheers

Llama and Tasker links broken

The Llama and Tasker links in README.md seem to be broken.

fix FileUriExposedException on sending logs

android.os.FileUriExposedException: file:///storage/emulated/0/trackworktime/log.txt exposed beyond app through ClipData.Item.getUri()
	at android.os.StrictMode.onFileUriExposed(StrictMode.java:1960)
	at android.net.Uri.checkFileUriExposed(Uri.java:2356)
	at android.content.ClipData.prepareToLeaveProcess(ClipData.java:942)
	at android.content.Intent.prepareToLeaveProcess(Intent.java:9850)
	at android.content.Intent.prepareToLeaveProcess(Intent.java:9856)
	at android.content.Intent.prepareToLeaveProcess(Intent.java:9835)
	at android.app.Instrumentation.execStartActivity(Instrumentation.java:1796)
	at android.app.Activity.startActivityForResult(Activity.java:4514)
	at android.support.v4.app.BaseFragmentActivityApi16.startActivityForResult(BaseFragmentActivityApi16.java:54)
	at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:68)
	at android.app.Activity.startActivityForResult(Activity.java:4472)
	at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:751)
	at android.app.Activity.startActivity(Activity.java:4833)
	at android.app.Activity.startActivity(Activity.java:4801)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.doSendLogs(WorkTimeTrackerActivity.java:801)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.lambda$sendLogs$11$WorkTimeTrackerActivity(WorkTimeTrackerActivity.java:785)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity$$Lambda$11.onClick(Unknown Source:2)
	at com.android.internal.app.AlertController$ButtonHandler.handleMessage(AlertController.java:166)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6753)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:482)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)

remove week object with last event object from DB

When deleting events, also remove the corresponding week object from the database if the user currently removes the last event for that week. This way test events don't trigger flexi time calculation for weeks far in the past.

fix ArrayIndexOutOfBoundsException on permission request

java.lang.RuntimeException: Unable to start activity ComponentInfo{org.zephyrsoft.trackworktime/org.zephyrsoft.trackworktime.WorkTimeTrackerActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2927)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2988)
	at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4915)
	at android.app.ActivityThread.-wrap21(ActivityThread.java)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1637)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6682)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.onRequestPermissionsResult(WorkTimeTrackerActivity.java:870)
	at android.app.Activity.requestPermissions(Activity.java:4291)
	at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:507)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.backupToSdAutomatically(WorkTimeTrackerActivity.java:931)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.onCreate(WorkTimeTrackerActivity.java:206)
	at android.app.Activity.performCreate(Activity.java:6942)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1126)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2880)
	... 10 more
java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.onRequestPermissionsResult(WorkTimeTrackerActivity.java:870)
	at android.app.Activity.requestPermissions(Activity.java:4291)
	at android.support.v4.app.ActivityCompat.requestPermissions(ActivityCompat.java:507)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.backupToSdAutomatically(WorkTimeTrackerActivity.java:931)
	at org.zephyrsoft.trackworktime.WorkTimeTrackerActivity.onCreate(WorkTimeTrackerActivity.java:206)
	at android.app.Activity.performCreate(Activity.java:6942)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1126)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2880)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2988)
	at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:4915)
	at android.app.ActivityThread.-wrap21(ActivityThread.java)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1637)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6682)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)

reconfigure ACRA

ACRA should show a dialog or notification when a crash has happened

report generation does not honor event order

The report generation mechanism seems to have problems with the order in which events are interpreted if at any time a week's sum is negative.

Also see #21.

option to have a weekly flexi time instead of a global/monthly one

Or even a daily one

location is checked even when that option is disabled

The app should not request location updated when the corresponding options section "Track by Location" is disabled.

problem in time calculation

Vili Seppänen reported a problem after being clocked in over midnight. This bug causes the UI to crash immediately in the week following the being-clocked-in-over-midnight. After another week the UI starts working again but crashes when switching to the previous week.

The automatic clock-in/clock-out works nevertheless, only the UI is affected.

repair reports for Android Nougat and newer

When TWT runs on Android Nougat or newer, the following error occurs when exporting a report:

android.os.FileUriExposedException: file:///storage/emulated/0/Android/data/org.zephyrsoft.trackworktime/files/trackworktime/reports/sums-all-data-week-generated-at-2018-04-26-22-20-28.csv exposed beyond app through ClipData.Item.getUri()
        at android.os.StrictMode.onFileUriExposed(StrictMode.java:1960)
        at android.net.Uri.checkFileUriExposed(Uri.java:2348)
        at android.content.ClipData.prepareToLeaveProcess(ClipData.java:942)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9854)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9860)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9839)
        at android.app.Instrumentation.execStartActivity(Instrumentation.java:1610)
        at android.app.Activity.startActivityForResult(Activity.java:4487)
        at android.support.v4.app.BaseFragmentActivityApi16.startActivityForResult(BaseFragmentActivityApi16.java:54)
        at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:68)
        at android.app.Activity.startActivityForResult(Activity.java:4445)
        at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:751)
        at android.app.Activity.startActivity(Activity.java:4806)
        at android.app.Activity.startActivity(Activity.java:4774)
        at org.zephyrsoft.trackworktime.ReportsActivity.lambda$onCreate$2$ReportsActivity(ReportsActivity.java:166)
        at org.zephyrsoft.trackworktime.ReportsActivity$$Lambda$2.onClick(Unknown Source:2)

Also see: https://stackoverflow.com/questions/38200282/android-os-fileuriexposedexception-file-storage-emulated-0-test-txt-exposed

Multiple work locations

Thanks for a nice app! It has potential to save me from 5 mins a day of unimportant work after a policy change at my employer.

I have an office job that is split between two locations. It would be nice to location track both of them as work time automatically. SSID-tracking will not be as reliable or accurate for me, but it will be a second best workaround.

create ACRA collector on separate domain

choose one of the backends and install it on a separate subdomain of zephyrsoft.org so it does not interfere with other changes that are made there
change the app settings accordingly (include https instead of http if appropriate)

Report: Times by task (Daily)

Would it be too difficult to add a daily summarized report option? Exactly like the weekly report, but per-day.

I just might be able to do this myself (by 'copying' the weekly report), but I'm not really confident in my Android programming skills...

create possibility to send logs

The user should be enabled to willingly send his logs to the developer for examination.

One possibility: via logcat system call:
http://code.google.com/p/android-log-collector/source/browse/trunk/android-log-collector-lib/src/com/xtralogic/android/logcollector/lib/SendLogActivity.java

Another possibility: write log to a file (additionally to writing it to logcat):
http://blog.cindypotvin.com/creating-logs-in-android-applications/

use a logging framework

At the moment the app uses a handmade logger which formats messages. It would be better to use a standard library for logging.

Report: too high values on the task which was running during the generation

Of the two reports I have[1], each one has a crazy high value for the current week on the task which was running during the generation.

Eg.

150:25
128:47

[1] whose types are

sums-per-week-last-and-current-month
sums-per-week-last-and-current-year

Notification spam

Test info

App version: v1.0.4
Android Version: Emulator API26

A. When WorkTimeTrackerActivity is resumed

Make sure "Track Work Time Notifications" channel is set to "Make sound" (it's set to on by default), so that issue is more apparent
Click "Start Tracking"
Minimize app
Resume app and notification will go off every time

B. When tracking by wifi is enabled

Enable "Track Work Time Notifications" channel to "Make sound"
Set up wifi tracking
Click "Start tracking"
Notification sound goes off periodically

IllegalStateException: "not allowed to start service intent - app is in background" on Android 8+

java.lang.IllegalStateException: Not allowed to start service Intent { cmp=org.zephyrsoft.trackworktime/.location.LocationTrackerService (has extras) }: app is in background uid UidRecord{fbd005 u0a305 RCVR bg:+4m57s939ms idle procs:2 seq(223,223,223)}
	at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1538)
	at android.app.ContextImpl.startService(ContextImpl.java:1484)
	at android.content.ContextWrapper.startService(ContextWrapper.java:663)
	at org.zephyrsoft.trackworktime.Basics.startLocationTrackerService(Basics.java:361)
	at org.zephyrsoft.trackworktime.Basics.checkLocationBasedTracking(Basics.java:341)
	at org.zephyrsoft.trackworktime.Basics.safeCheckLocationBasedTracking(Basics.java:218)
	at org.zephyrsoft.trackworktime.Basics.periodicHook(Basics.java:196)
	at org.zephyrsoft.trackworktime.Watchdog.onReceive(Watchdog.java:34)
	at android.app.ActivityThread.handleReceiver(ActivityThread.java:3390)
	at android.app.ActivityThread.-wrap18(Unknown Source:0)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1780)
	at android.os.Handler.dispatchMessage(Handler.java:105)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6938)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

Starting with API level 21 (Android 5.0 Lollipop), the JobScheduler is available and apparently under Oreo it has to be used if the user didn't grant an exception.

Anyone may go to "Settings" -> "Apps & notifications" -> "Advanced" -> "Special app access" -> "Battery optimization", select "All apps", tap on "Track Work Time" in the list and select "Don't optimize". This will exclude TWT from some restrictions regarding background work.

Report: Not working on oreo

Reports export has stopped working when my phone was updated to oreo version.

Reproduce:

Select reports
Choose any report type (e.g. "last" + "month")
Click any export button (e.g. "all events")
Nothing happens

Device info:

Model: LG G6
Android: 8.0.0

Stack trace of error:

06-04 08:05:45.442 27503-27503/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: org.zephyrsoft.trackworktime, PID: 27503
    android.os.FileUriExposedException: file:///storage/emulated/0/Android/data/org.zephyrsoft.trackworktime/files/trackworktime/reports/events-last-month-generated-at-2018-06-04-08-05-45.csv exposed beyond app through ClipData.Item.getUri()
        at android.os.StrictMode.onFileUriExposed(StrictMode.java:1958)
        at android.net.Uri.checkFileUriExposed(Uri.java:2359)
        at android.content.ClipData.prepareToLeaveProcess(ClipData.java:941)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9756)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9762)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9741)
        at android.app.Instrumentation.execStartActivity(Instrumentation.java:1611)
        at android.app.Activity.startActivityForResult(Activity.java:4479)
        at android.support.v4.app.BaseFragmentActivityJB.startActivityForResult(BaseFragmentActivityJB.java:48)
        at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:75)
        at android.app.Activity.startActivityForResult(Activity.java:4437)
        at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:856)
        at android.app.Activity.startActivity(Activity.java:4798)
        at android.app.Activity.startActivity(Activity.java:4766)
        at org.zephyrsoft.trackworktime.ReportsActivity$1.onClick(ReportsActivity.java:125)
        at android.view.View.performClick(View.java:6274)
        at android.view.View$PerformClick.run(View.java:24859)
        at android.os.Handler.handleCallback(Handler.java:789)
        at android.os.Handler.dispatchMessage(Handler.java:98)
        at android.os.Looper.loop(Looper.java:164)
        at android.app.ActivityThread.main(ActivityThread.java:6710)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:770)
06-04 08:05:45.442 27503-27503/? E/ACRA: ACRA caught a FileUriExposedException for org.zephyrsoft.trackworktime
    android.os.FileUriExposedException: file:///storage/emulated/0/Android/data/org.zephyrsoft.trackworktime/files/trackworktime/reports/events-last-month-generated-at-2018-06-04-08-05-45.csv exposed beyond app through ClipData.Item.getUri()
        at android.os.StrictMode.onFileUriExposed(StrictMode.java:1958)
        at android.net.Uri.checkFileUriExposed(Uri.java:2359)
        at android.content.ClipData.prepareToLeaveProcess(ClipData.java:941)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9756)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9762)
        at android.content.Intent.prepareToLeaveProcess(Intent.java:9741)
        at android.app.Instrumentation.execStartActivity(Instrumentation.java:1611)
        at android.app.Activity.startActivityForResult(Activity.java:4479)
        at android.support.v4.app.BaseFragmentActivityJB.startActivityForResult(BaseFragmentActivityJB.java:48)
        at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:75)
        at android.app.Activity.startActivityForResult(Activity.java:4437)
        at android.support.v4.app.FragmentActivity.startActivityForResult(FragmentActivity.java:856)
        at android.app.Activity.startActivity(Activity.java:4798)
        at android.app.Activity.startActivity(Activity.java:4766)
        at org.zephyrsoft.trackworktime.ReportsActivity$1.onClick(ReportsActivity.java:125)
        at android.view.View.performClick(View.java:6274)
        at android.view.View$PerformClick.run(View.java:24859)
        at android.os.Handler.handleCallback(Handler.java:789)
        at android.os.Handler.dispatchMessage(Handler.java:98)
        at android.os.Looper.loop(Looper.java:164)
        at android.app.ActivityThread.main(ActivityThread.java:6710)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:770)```

backup/restore does not honor event order

The back/restore mechanism (which exports all events into a flat CSV) sometimes has problems restoring these events when they appear in the CSV file in an order so that at any point the week's sum is negative.

Possible solution: Export events in exactly the order in which they are interpreted by TWT normally (old before new, if timestamp is equal: "out" before "in").

UI polishing

The UI could be much more friendly and shiny, for example:
In the events list, show the event type by an icon and not just by the text "IN" and "OUT".

track by more than one SSID

Enable the user to track by more than 1 wifi SSID, e.g. track task1 when in range of ssid1 and track task2 when in range of ssid2.

Or, to simplify the task, track only the default task (not different tasks), but the user can configure more than one SSID for the range check.

It's not easy to implement this the generic way because SSIDs can contain any character, also spaces, commas and semicolons. So a list of SSIDs which can be configured in one single input field would remove support for SSIDs containing the separator character, therefore this solution is not suitable.