[LeakScope] 3 Android lifecycle/memory violations detected

## 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](https://github.com/soot-oss/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 **3 potential issue(s)** across **1 detector type(s)**:

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

| Detector | Count | Severity | Description |
|---|---|---|---|
| `ViewBindingOpportunity` | 3 | 🟢 Low | Manual findViewById() calls — ViewBinding migration opportunity |

---

### Detailed Findings

#### 🟢 `ViewBindingOpportunity`
*Manual findViewById() calls — ViewBinding migration opportunity*

**Finding #1 — `MainActivity`**

```
View Binding Migration Opportunity
Class: com.ayush.steganography.MainActivity
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
• findViewById in onCreate
• findViewById in onCreate
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 #2 — `Encode`**

```
View Binding Migration Opportunity
Class: com.ayush.steganography.Encode
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
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 #3 — `Decode`**

```
View Binding Migration Opportunity
Class: com.ayush.steganography.Decode
Type: Activity
Current Pattern: Manual view lookup
findViewById() Calls:
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
• findViewById in onCreate
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](https://github.com/). Tool analyzes compiled APKs using Soot static analysis on [Image-Steganography-Library-Android](https://github.com/aagarwal1012/Image-Steganography-Library-Android).*