⚡ Bolt: Filter high-frequency CompassSensor emissions#105
Conversation
- Added 1-degree change threshold in `CompassSensor.kt` `onSensorChanged` loop - Drastically reduces `CompassData` object allocation and GC churn at 60Hz - Prevents expensive downstream UI recomposition in `NachsucheScreen.kt` - Added performance insight to `.jules/bolt.md` Co-authored-by: nacl-dev <243312305+nacl-dev@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
💡 What: Added a 1-degree change threshold before creating and emitting a new
CompassDataobject in the high-frequencyonSensorChangedevent loop withinCompassSensor.kt.🎯 Why: Sensors firing at
SENSOR_DELAY_UI(approx. 60Hz) were unconditionally creating and emitting newCompassDataobjects on every tick, even when the device was completely stationary. This caused significant Garbage Collection (GC) churn and forced downstream collectors—specifically the UI inNachsucheScreen.kt—to aggressively recompose 60 times a second, consuming CPU, battery, and causing UI micro-stutters.📊 Impact: Reduces object allocations and Jetpack Compose recompositions related to the compass by up to 90% (when the device is mostly steady), while maintaining precise functionality and a visually smooth UI.
🔬 Measurement: Verify by running the application and tracking the memory profiler or Compose Recomposition counters in Android Studio; the churn will only occur when the device is actively rotated >1 degree instead of continuously.
PR created automatically by Jules for task 11615784152286625368 started by @nacl-dev