Urgent: Fix Sensor Configuration and UI Persistence Issues in AWARE Android Framework

---

---

I'm seeking an experienced Android developer to resolve two critical issues with the AWARE Framework Android client. AWARE is a mobile context instrumentation framework used for data collection in research studies. Background: The AWARE framework allows researchers to configure sensors remotely through study configurations. Users can also manually enable/disable sensors through the app's UI. Currently, there are two related issues affecting sensor configuration and persistence. Problem 1: Sensor Status Inconsistency in UI When a study is configured with certain sensors set to 'on', these sensors sometimes appear as 'off' in the AWARE UI. This creates confusion for participants and researchers as the visual state does not match the actual configuration. The issue appears to be in how the study configuration is applied and how the UI reflects the sensor status. Problem 2: Manual Sensor Changes Not Persisting When users manually change sensor settings through the app interface, these changes are not properly persisted. After app restart or in some cases immediately after changing settings, the sensors revert to their previous state. This makes it impossible for users to reliably configure their sensors through the UI. Technical Details: - Android Framework: API level 34 (Android 14) - The codebase is primarily Java with some Kotlin - Settings are managed through Aware.setSetting() method and stored in SharedPreferences - Study configurations are applied through Aware.tweakSettings() method - The UI reflects sensor states using CheckBoxPreference components - When preferences change, onSharedPreferenceChanged() should update both the UI and the underlying settings Specific areas to investigate: 1. The SharedPreferences listener in Aware_Client.java and how it processes changes 2. The synchronization between study configuration settings and UI state 3. The persistence mechanism for manual changes to sensor settings 4. Potential race conditions between the UI thread and background services 5. The handling of preference changes in the executeSettingsSync() and updatePreference() methods Deliverables: 1. A fix for both issues that ensures: - Sensors configured as 'on' in study config correctly appear as 'on' in the UI - Manual sensor changes persist across app restarts and background/foreground transitions 2. Comprehensive explanation of the root causes of both issues 3. Make sure the fix works on android 14. Requirements: - Strong experience with Android development, particularly UI components and SharedPreferences - Familiarity with preference management in Android applications - Experience debugging UI state inconsistencies and persistence issues - Knowledge of thread safety and race conditions in Android Timeline: This is an urgent issue affecting study participants. I'm looking for someone who can start immediately Additional notes: - Access to the source code will be provided upon selection - The fix should be backward compatible with existing implementations - You will have access to the current development team for any questions about the codebase

Keyword: App Development

Price: $50.0

Kotlin Android SDK Smartphone Android Java MySQL Database Management Software Debugging