Urgent: Fix Remote Server Device Identification Issue in AWARE Android Client Framework

---

---

I'm seeking an experienced Android developer to resolve an issue with the AWARE Framework Android client. The framework is failing to update the remote server's 'aware_device' table with the correct device label after joining a study. Background: The AWARE framework is an Android application used for data collection in research studies. When a device joins a study, it should update its device_id and label in both the local database and the remote server's 'aware_device' table. Currently, while the local database is updated correctly, this information is not being properly propagated to the remote server. Problem: After a user joins a study, the 'aware_device' table on the remote server is not being updated with the correct device_id and label. This creates issues with device identification and data attribution on the server side. While data is being collected and even synced to the server, the device's identifying information in the 'aware_device' table remains outdated or missing. Specifically: 1. The local device database correctly updates with the device_id and label 2. The ContentValues with the device label are created correctly (in Aware.java) 3. The local ContentProvider (Aware_Provider) processes the update properly 4. However, this update is not being properly synchronized to the remote server's 'aware_device' table Technical Details: - Android Framework: API level 34 (Android 14) - The codebase is primarily Java with some Kotlin - You should make sure that the fix does not cause regression issues on the sensors mechanism Send me a message to get access to the code base, app installation instructions, and access to the database.

Keyword: App Development

Price: $70.0

Kotlin Android SDK Smartphone Android Java MySQL Database Management Software Debugging