How normancao2702/cmpt362-myruns works
Project type and purpose
• This is an Android mobile application (“MyRuns”) for tracking exercise sessions (run, walk, climb, unknown) by sampling the device accelerometer and GPS, storing history locally in a Room database, and displaying maps via Google Maps API.
File structure
• Top-level “app/src/main/java/com/example/tranquangngoc_cao_myruns2” contains subpackages:
• automatic – sensor sampling, FFT, Weka classifier, global constants
• database – Room entities, DAO, database class, migrations, repository
• googleMap – ViewModel, Activities/Services for map display & location tracking
• historyFragment & historyDetail – fragment for list of past entries and detailed display
• manualActivity – manual entry UI
• startFragment, settingFragment, userProfile – UI navigation & user settings
• util – shared utilities (unit conversion, helpers)
• AndroidManifest.xml, Gradle scripts, resource directories (layouts, drawables, values) are standard.
README for additional insights
• Confirms features: location & speed tracking, exercise classification, photo upload, unit preferences.
• Dependencies: Android API 33+, Room database, Google Play Services (Maps), Weka for classification.
Main components and their relationships
a. Components
1. UI Layer
– Activities & Fragments: MainActivity (host), StartFragment, HistoryFragment, SettingsFragment, UserProfileActivity, ManualEntryActivity, DisplayEntryActivity, MapDisplayActivity, MapDetailActivity
2. ViewModels (in googleMap & possibly injected in Fragments)
3. Background Services
– SensorService: samples accelerometer, forwards data to WekaClassifier via Globals
– TrackingService: obtains location updates for mapping & distance/speed calculations
4. Automatic Classification
– FFT: feature extraction
– WekaClassifier: ML model inference (Run, Walk, Climb, Unknown)
5. Data Layer
– ExerciseDatabase (Room)
– ExerciseEntry entity & DAO
– ExerciseRepository: interface between ViewModels/Activities/Services and the database
6. External Services
– Google Maps API for map display & routing
– Android system sensors (accelerometer, location API)
b. Data flow & interactions
• User interacts with UI → triggers ViewModel methods → reads/writes via ExerciseRepository → Room database
• Background SensorService samples accelerometer → processes data (FFT) → WekaClassifier → writes classification + timestamp to database via Repository
• TrackingService collects GPS coordinates → emits updates to MapViewModel → UI map updates in MapDisplayActivity/MapDetailActivity
• SettingsFragment updates user preferences (units, notifications) stored in SharedPreferences or Globals
• HistoryFragment retrieves list of ExerciseEntry records via Repository → displays in RecyclerView
Architectural patterns & design principles
• MVVM (Model-View-ViewModel): separates UI (Activities/Fragments) from business logic (ViewModels) and data (Repository + Room)
• Repository pattern: abstracts Room database operations behind a clean API
• Service-based background processing: SensorService & TrackingService run as foreground services for continuous sampling
• Modular package structure: by feature (automatic, database, googleMap, history, manual, settings, etc.)
Relevant technologies & libraries
• Kotlin + Android Jetpack (Room, ViewModel, LiveData/DataBinding)
• Google Play Services: Maps and Location
• Weka ML library (for on-device classification)
• FFT algorithm implementation for feature extraction
• Coroutines or standard threading (if present) for async database/service tasks