Android watch app playstore update

[sijitg]

Android wear app - Update Target SDK version to latest to meet play store submission criteria
Replace Kotlin synthetics with View binding
Fix the issues in Wear app Github actions workflow file

[sijitg]

Libraries updated
Kotlin synthetics replaced with view binding
We are doing developer testing in a Google Pixel Watch Wear OS version 3.5

[sijitg]

we uploaded watch build to Playstore internal for testing, but some old dependencies are throwing errors . We are checking it.

[sijitg]

@carsten we need to remove Aware components also before pushing the build to playstore. Please confirm whether to proceed.

[sijitg]

We would like to discuss about this task in this week's meeting and proceed from there.

[sijitg]

We started working on this. Based on the last discussion we will include necessary permission popup and submit to play store with Aware components.

[sijitg]

We submitted an internal test version to Play store . But after further testing we found Aware is throwing more errors due to compatibility issues with Android 11 .
Following issue is blocking us.
denzilferreira/aware-client#303

[sijitg]

We checked to use existing Lamp SDK but effort is involved to replace Google Fit API with Health Services on Wear OS .
https://developer.android.com/training/wearables/health-services

@ertjlane

[sijitg]

Following is the current status of Android Watch app development.
While testing we found that Aware framework is throwing errors due to Android 11 target version compatibility issues. We need to either wait for Aware framework developers to update the same or we can use Lamp's SDK which we are using in Mobile app.
But to use Lamp SDK in watch app we need to write wrapper code for integrating Health Services for Wear OS.
We would like to discuss this in meeting
@ertjlane

[carlan1]

If you were to remove aware components and instead use LAMP SDK, how will this impact sensor data collection for android wearables?

[sijitg]

If you were to remove aware components and instead use LAMP SDK, how will this impact sensor data collection for android wearables?

we need to write wrapper code for integrating Health Services for Wear OS, see below link.

https://developer.android.com/training/wearables/health-services

[carlan1]

How will this affect lower level sensors like accelerometer, gps, etc?

[sijitg]

Health Services for Wear OS provides data types which include Steps, Distance, Elevation, Speed, Location data(Latitude, longitude and optionally, altitude and bearing at a specific point in time) etc.
Please see below link for list of data
https://developer.android.com/reference/kotlin/androidx/health/services/client/data/DataType
Android SensorManager API to be used for any other Data
We have seen the following discussion which says "After using Wear Health Services , the accelerator sensor data cannot be sampled with the specified sample rate" which we need to confirm whether affect us also.
android/health-samples#9
@carlan1

[carlan1]

Good to proceed

[ZCOEngineer]

Ok @carlan1

[sijitg]

We started working on this.

[sijitg]

Using Health services we are able to read data such as Heart beat and steps . Integration is in progress.

[michaelmenon]

@carlan1 Status update on Watch app update : We have removed Aware framework code and integrated Health services for Wear OS and we are able to collect data such as Heart rate , Location and send to server.
After integrating remaining sensors we expect to send a test build by 06/16/2023, Friday

[sijitg]

@carlan1 Android watch app staging build is available for testing in Play store Internal track. It can be tested by opt- in to following URL.
https://play.google.com/apps/internaltest/4698721810376871205

Please provide the google account using which you would like to test the app. We need to add these accounts in Testers list in Google play console so that you get invitation to test the app.
Please note build submitted to internal test track are immediately made available for testing with out Google's approval process. Before submitting to production we need to do some more optimization.