[LeakScope] 5 Android lifecycle/memory violations detected

[MuhammadTehamsibAliTashfeen]

LeakScope: Android Lifecycle & Memory Leak Violations

About this report: This issue was automatically generated by LeakScope, a static analysis tool for Android lifecycle violations and memory leaks built on the Soot framework. This is part of an ongoing academic research study targeting ICSE 2027. No immediate action is required — we would greatly appreciate your feedback on whether these findings are accurate.

Summary

LeakScope detected 5 potential issue(s) across 2 detector type(s):

Severity	Count
🔴 High	0
🟡 Medium	2
🟢 Low (improvement opportunity)	3

Detector	Count	Severity	Description
ServiceResourceManagementIssueDetector	2	🟡 Medium	Service may never stop — missing stopSelf() call
ViewBindingOpportunity	3	🟢 Low	Manual findViewById() calls — ViewBinding migration opportunity

---

Detailed Findings

🟡 ServiceResourceManagementIssueDetector

Service may never stop — missing stopSelf() call

Finding #1 — StepService

⚠� Service may never stop. Consider calling stopSelf() when work is complete.
  Class: cn.bluemobi.dylan.step.step.service.StepService
  Method: onStartCommand

Finding #2 — StepsDetectService

⚠� Service may never stop. Consider calling stopSelf() when work is complete.
  Class: cn.bluemobi.dylan.step.pedometer.StepsDetectService
  Method: onStartCommand

🟢 ViewBindingOpportunity

Manual findViewById() calls — ViewBinding migration opportunity

Finding #3 — HistoryActivity

View Binding Migration Opportunity
Class: cn.bluemobi.dylan.step.activity.HistoryActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
Benefits of View Binding:
- Eliminates boilerplate findViewById() calls
- Compile-time type safety for view references
- Reduced null pointer exceptions
- Cleaner, more maintainable code
Note: This is a code modernization suggestion, not a memory leak

Finding #4 — MainActivity

View Binding Migration Opportunity
Class: cn.bluemobi.dylan.step.activity.MainActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
Benefits of View Binding:
- Eliminates boilerplate findViewById() calls
- Compile-time type safety for view references
- Reduced null pointer exceptions
- Cleaner, more maintainable code
Note: This is a code modernization suggestion, not a memory leak

Finding #5 — SetPlanActivity

View Binding Migration Opportunity
Class: cn.bluemobi.dylan.step.activity.SetPlanActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
  • findViewById in assignViews
Benefits of View Binding:
- Eliminates boilerplate findViewById() calls
- Compile-time type safety for view references
- Reduced null pointer exceptions
- Cleaner, more maintainable code
Note: This is a code modernization suggestion, not a memory leak

---

How to respond to this issue:

• If a finding is a true positive: consider applying the recommended fix and closing this issue.
• If a finding is a false positive: please leave a comment explaining why — your feedback directly improves our research.
• If you have questions: reply here or open a discussion.

This report was generated by LeakScope as part of the ICSE 2027 research artifact. Tool analyzes compiled APKs using Soot static analysis on DylanStepCount.