-
Notifications
You must be signed in to change notification settings - Fork 50
Expand file tree
/
Copy pathAndroidManifest.xml
More file actions
211 lines (201 loc) · 12.2 KB
/
Copy pathAndroidManifest.xml
File metadata and controls
211 lines (201 loc) · 12.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools">
<!-- BLE: Android 12+ uses BLUETOOTH_SCAN/CONNECT; older needs location for scan. -->
<uses-permission android:name="android.permission.BLUETOOTH_SCAN"
android:usesPermissionFlags="neverForLocation" />
<uses-permission android:name="android.permission.BLUETOOTH_CONNECT" />
<uses-permission android:name="android.permission.BLUETOOTH" android:maxSdkVersion="30" />
<uses-permission android:name="android.permission.BLUETOOTH_ADMIN" android:maxSdkVersion="30" />
<!-- Location: FINE/COARSE are used for two things — (a) BLE scan on API <=30
(legacy requirement), and (b) GPS workout-route tracking on all API levels
(while-in-use). Because of (b) the FINE permission is NOT capped at API 30. -->
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<!-- FGS location type (API 34+): lets EdgeTrackingService keep sampling GPS while
a run/ride/walk session is active and the app is backgrounded. -->
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_LOCATION" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<!-- Edge Tracking foreground service: keeps the strap connection alive in the background. -->
<uses-permission android:name="android.permission.FOREGROUND_SERVICE" />
<uses-permission android:name="android.permission.FOREGROUND_SERVICE_CONNECTED_DEVICE" />
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />
<!-- Band-gesture "ring my phone" haptic. Normal permission, no runtime prompt. -->
<uses-permission android:name="android.permission.VIBRATE" />
<!-- Reboot survival: restart EdgeTrackingService + headless auto-connect after device reboot. -->
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<!-- CompanionDeviceManager: association makes us a "companion app" (exempt from the
API 31+ background foreground-service-start restriction) and lets the OS relaunch
us (EdgeCompanionService) when the associated band comes into range. -->
<uses-permission android:name="android.permission.REQUEST_COMPANION_RUN_IN_BACKGROUND" />
<uses-permission android:name="android.permission.REQUEST_COMPANION_USE_DATA_IN_BACKGROUND" />
<uses-permission android:name="android.permission.REQUEST_OBSERVE_COMPANION_DEVICE_PRESENCE" />
<!-- Battery-optimization (Doze) exemption request — user-granted via the system
dialog fired from the "Keep alive in background" row. -->
<uses-permission android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" />
<!-- Keep the CPU alive while the boot receiver starts the foreground service. -->
<uses-permission android:name="android.permission.WAKE_LOCK" />
<!-- OTA self-update: download + launch the system installer for the new APK. -->
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" />
<!-- Notification relay: let the user pick from their installed apps. Android 11+
hides the package list without this; OpenStrap ships as a sideloaded APK (not
Play-distributed), so broad visibility is acceptable here. -->
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES"
tools:ignore="QueryAllPackagesPermission" />
<!-- ── Health Connect (export to Google Health Connect) ──
The `health` plugin treats a WRITE request as READ+WRITE (hasPermissions
checks both), so the READ_* permissions MUST be declared too even though
we only write. -->
<uses-permission android:name="android.permission.health.READ_HEART_RATE" />
<uses-permission android:name="android.permission.health.WRITE_HEART_RATE" />
<uses-permission android:name="android.permission.health.READ_RESTING_HEART_RATE" />
<uses-permission android:name="android.permission.health.WRITE_RESTING_HEART_RATE" />
<uses-permission android:name="android.permission.health.READ_HEART_RATE_VARIABILITY" />
<uses-permission android:name="android.permission.health.WRITE_HEART_RATE_VARIABILITY" />
<uses-permission android:name="android.permission.health.READ_RESPIRATORY_RATE" />
<uses-permission android:name="android.permission.health.WRITE_RESPIRATORY_RATE" />
<uses-permission android:name="android.permission.health.READ_ACTIVE_CALORIES_BURNED" />
<uses-permission android:name="android.permission.health.WRITE_ACTIVE_CALORIES_BURNED" />
<uses-permission android:name="android.permission.health.READ_BASAL_METABOLIC_RATE" />
<uses-permission android:name="android.permission.health.WRITE_BASAL_METABOLIC_RATE" />
<uses-permission android:name="android.permission.health.READ_STEPS" />
<uses-permission android:name="android.permission.health.WRITE_STEPS" />
<uses-permission android:name="android.permission.health.READ_SLEEP" />
<uses-permission android:name="android.permission.health.WRITE_SLEEP" />
<uses-permission android:name="android.permission.health.READ_EXERCISE" />
<uses-permission android:name="android.permission.health.WRITE_EXERCISE" />
<uses-feature android:name="android.hardware.bluetooth_le" android:required="true" />
<!-- CompanionDeviceManager availability (not required: devices without it just skip
the association and rely on the sticky service + watchdog). -->
<uses-feature android:name="android.software.companion_device_setup"
android:required="false" />
<application
android:label="Edge"
android:name=".EdgeApplication"
android:icon="@mipmap/launcher_icon">
<activity
android:name=".MainActivity"
android:exported="true"
android:launchMode="singleTop"
android:taskAffinity=""
android:theme="@style/LaunchTheme"
android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
android:hardwareAccelerated="true"
android:windowSoftInputMode="adjustResize">
<!-- Specifies an Android theme to apply to this Activity as soon as
the Android process has started. This theme is visible to the user
while the Flutter UI initializes. After that, this theme continues
to determine the Window background behind the Flutter UI. -->
<meta-data
android:name="io.flutter.embedding.android.NormalTheme"
android:resource="@style/NormalTheme"
/>
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<!-- Health Connect: permission-rationale entry point (required). -->
<intent-filter>
<action android:name="androidx.health.ACTION_SHOW_PERMISSIONS_RATIONALE" />
</intent-filter>
</activity>
<!-- Health Connect rationale for Android 14+ (VIEW_PERMISSION_USAGE). -->
<activity-alias
android:name="ViewPermissionUsageActivity"
android:exported="true"
android:targetActivity=".MainActivity"
android:permission="android.permission.START_VIEW_PERMISSION_USAGE">
<intent-filter>
<action android:name="android.intent.action.VIEW_PERMISSION_USAGE" />
<category android:name="android.intent.category.HEALTH_PERMISSIONS" />
</intent-filter>
</activity-alias>
<!-- Edge Tracking foreground service (background BLE drain). -->
<service
android:name=".EdgeTrackingService"
android:exported="false"
android:foregroundServiceType="connectedDevice|location" />
<!-- CompanionDeviceService (API 31+): the OS binds this when the associated band
comes into range (startObservingDevicePresence) — onDeviceAppeared restarts
the tracking service, so background capture recovers even after a process
kill. Never bound below API 31 (the action doesn't exist there). -->
<service
android:name=".EdgeCompanionService"
android:exported="true"
android:permission="android.permission.BIND_COMPANION_DEVICE_SERVICE">
<intent-filter>
<action android:name="android.companion.CompanionDeviceService" />
</intent-filter>
</service>
<!-- Boot receiver: restarts EdgeTrackingService + headless auto-connect after reboot.
Handles BOOT_COMPLETED + QUICKBOOT_POWERON. -->
<receiver
android:name=".BootReceiver"
android:exported="true"
android:enabled="true">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
<action android:name="android.intent.action.QUICKBOOT_POWERON" />
</intent-filter>
</receiver>
<!-- Tasker integration: receive Broadcast intents from Tasker (or any app)
to buzz the WHOOP strap. Optional int extra "pattern" (default 2). -->
<receiver
android:name=".TaskerReceiver"
android:exported="true"
android:enabled="true">
<intent-filter>
<action android:name="wtf.openstrap.openstrap_edge.BUZZ_STRAP" />
</intent-filter>
</receiver>
<!-- Notification relay (notification_listener_service plugin). The system binds
this to deliver posted notifications; gated behind the user granting
"Notification access" in system settings. Class lives in the plugin. -->
<service
android:name="notification.listener.service.NotificationListener"
android:label="OpenStrap notification relay"
android:permission="android.permission.BIND_NOTIFICATION_LISTENER_SERVICE"
android:exported="true">
<intent-filter>
<action android:name="android.service.notification.NotificationListenerService" />
</intent-filter>
</service>
<!-- OTA self-update (ota_update 7.x). The plugin's LIBRARY manifest only
declares permissions — the host app MUST declare this FileProvider +
receiver itself, or the install handoff throws "Couldn't find meta-data
for provider with authority ...ota_update_provider" and crashes at 100%. -->
<provider
android:name="sk.fourq.otaupdate.OtaUpdateFileProvider"
android:authorities="${applicationId}.ota_update_provider"
android:exported="false"
android:grantUriPermissions="true">
<meta-data
android:name="android.support.FILE_PROVIDER_PATHS"
android:resource="@xml/filepaths" />
</provider>
<receiver
android:name="sk.fourq.otaupdate.InstallResultReceiver"
android:exported="false">
<intent-filter>
<action android:name="${applicationId}.ACTION_INSTALL_COMPLETE" />
</intent-filter>
</receiver>
<!-- Don't delete the meta-data below.
This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
<meta-data
android:name="flutterEmbedding"
android:value="2" />
</application>
<!-- Required to query activities that can process text, see:
https://developer.android.com/training/package-visibility and
https://developer.android.com/reference/android/content/Intent#ACTION_PROCESS_TEXT.
In particular, this is used by the Flutter engine in io.flutter.plugin.text.ProcessTextPlugin. -->
<queries>
<intent>
<action android:name="android.intent.action.PROCESS_TEXT"/>
<data android:mimeType="text/plain"/>
</intent>
<!-- Health Connect app discovery (for install/status checks). -->
<package android:name="com.google.android.apps.healthdata" />
</queries>
</manifest>