Gadgetbridge/app/src/main/res/layout/activity_configure_alarms.xml

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent"
    android:layout_height="match_parent" android:paddingLeft="@dimen/activity_horizontal_margin"
    android:paddingRight="@dimen/activity_horizontal_margin"
    android:paddingTop="@dimen/activity_vertical_margin"
    android:paddingBottom="@dimen/activity_vertical_margin"
    tools:context="nodomain.freeyourgadget.gadgetbridge.activities.ConfigureAlarms">

    <ListView
        android:descendantFocusability="blocksDescendants"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:id="@android:id/list"
        android:layout_alignParentTop="true"
        android:layout_centerHorizontal="true" />
</RelativeLayout>
Initial implementation of setting alarms to the Mi Band. The code basically works, but there a lot of things to fix / improve. * The alarms are stored to and read from the Shared Preferences, but there is no persistence within the app (basically they are read and stored at every access) * The alarm list is not updated when coming back from the alarm detail view (probably related to the point above), but the actual alarm is * The alarms preference names is sometimes built by concatenating strings, which is not really safe * There is no check in the alarm constructor whether the stored string is a valid alarm representation * Even though only 3 alarms can be stored on the device, we could have more in the app and let the user choose which to sync * In the alarm detail view XML some material* drawables are used, it's possible that these break on android version < 5 * ... 2015-06-24 20:14:08 +02:00			`<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"`
			`xmlns:tools="http://schemas.android.com/tools" android:layout_width="match_parent"`
			`android:layout_height="match_parent" android:paddingLeft="@dimen/activity_horizontal_margin"`
			`android:paddingRight="@dimen/activity_horizontal_margin"`
			`android:paddingTop="@dimen/activity_vertical_margin"`
			`android:paddingBottom="@dimen/activity_vertical_margin"`
			`tools:context="nodomain.freeyourgadget.gadgetbridge.activities.ConfigureAlarms">`

			`<ListView`
			`android:descendantFocusability="blocksDescendants"`
			`android:layout_width="wrap_content"`
			`android:layout_height="wrap_content"`
further improvements: - the day of week are evenly spread across the screen in the alarms detail activity - the alarms are stored in a single shared preference (as a set) NB: you'll have to reset your alarms if you used a previous version (and also manually clean the shared preferences, but this is not needed) - the list of alarms gets correctly updated after editing a specific alarm - the actionbar back button saves the alarm status, the device back button doesn't. I'm not sure if it's a bug or a feature :) 2015-06-26 17:22:42 +02:00			`android:id="@android:id/list"`
Initial implementation of setting alarms to the Mi Band. The code basically works, but there a lot of things to fix / improve. * The alarms are stored to and read from the Shared Preferences, but there is no persistence within the app (basically they are read and stored at every access) * The alarm list is not updated when coming back from the alarm detail view (probably related to the point above), but the actual alarm is * The alarms preference names is sometimes built by concatenating strings, which is not really safe * There is no check in the alarm constructor whether the stored string is a valid alarm representation * Even though only 3 alarms can be stored on the device, we could have more in the app and let the user choose which to sync * In the alarm detail view XML some material* drawables are used, it's possible that these break on android version < 5 * ... 2015-06-24 20:14:08 +02:00			`android:layout_alignParentTop="true"`
			`android:layout_centerHorizontal="true" />`
			`</RelativeLayout>`