How kayamasoft/ksmeasuring works
Project type and purpose
• This is a native Android application (“app” module) written in Kotlin/Jetpack Compose.
• Its goal is to collect and display mobile network metrics (RSRP, SINR, RSRQ, speeds), graph histories, and record logs as CSV.
File structure
Top-level:
• build files (Gradle Kotlin DSL)
• “app/” module containing APK output, Proguard, source, resources, tests
app/src/main/java/com/kayamasoft/ksmeasuring:
• MainActivity.kt – host for the Compose UI
• SignalLoggingService.kt – background Service for polling and logging
• BandMapper.kt – helper to map raw radio parameters
• ui/theme – Compose theming
app/src/main/res: layouts, drawables, XML rules (backup, data extraction)
Tests in androidTest/ and test/
README insights
• Uses Android permissions (location, phone state, network, storage)
• Writes CSV under /Documents/ksmeasuring
• Displays graphs (RSRP history), tables, neighbor-cell lists
Main components and their interactions
A. Android UI Layer
– MainActivity + Compose screens for:
• Real-time metrics display
• Neighbor-cell list
• RSRP history graph
• CSV log download interface
B. SignalLoggingService (Background Service)
– Runs on a periodic scheduler or bound by the UI
– Invokes Android TelephonyManager, ConnectivityManager, LocationManager to fetch: RSRP, SINR, RSRQ, speed, neighbors
– Emits updates via a local Binder or LiveData/Flow
– Appends records to CSV file in external storage
C. File Storage
– Android File API writing to Documents/ksmeasuring/*.csv
D. Android OS Telephony & Network APIs
– TelephonyManager for radio metrics
– ConnectivityManager for data rates
– LocationManager for cell info if needed
E. Optional Charting Library (third-party or Compose Canvas)
– Renders RSRP history graph
Architectural patterns and principles
• Separation of concerns: UI vs. background measurement vs. storage
• Service pattern: long-running work in SignalLoggingService
• Unidirectional data flow: Service → UI observers → screens
• Single Android module: no microservices or remote backend