Skip to content

fix: enable editability for all switches - #41

Open
SayanthRock wants to merge 1 commit into
mainfrom
fix-editable-switches-13110576293345673495
Open

fix: enable editability for all switches#41
SayanthRock wants to merge 1 commit into
mainfrom
fix-editable-switches-13110576293345673495

Conversation

@SayanthRock

@SayanthRock SayanthRock commented Aug 9, 2026

Copy link
Copy Markdown
Owner

User description

Changed option.setEnabled(!required); to option.setEnabled(true); so that all toggles are fully editable to meet the requirement "Everything on this device should be editable and everything should be fine."


PR created automatically by Jules for task 13110576293345673495 started by @SayanthRock


CodeAnt-AI Description

Make every system customization switch editable

What Changed

  • Required switches can now be toggled on or off instead of being locked
  • All switch changes are saved and show the existing enabled or disabled confirmation

Impact

✅ Editable required settings
✅ Full control over device customization options
✅ Clear toggle confirmation

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Summary by CodeRabbit

  • Bug Fixes
    • Required profile switches are now enabled and interactive.
    • Changes to required profiles are saved correctly, matching optional profile behavior.

Co-authored-by: SayanthRock <202829406+SayanthRock@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Copilot AI lite review requested due to automatic review settings August 9, 2026 13:30
@devloai

devloai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Unable to trigger custom agent "Code Reviewer". You have run out of credits 😔
Please upgrade your plan or buy additional credits from the subscription page.

@codeant-ai

codeant-ai Bot commented Aug 9, 2026

Copy link
Copy Markdown

🤖 CodeAnt AI — Review Status

Status Commit Started (UTC) Finished (UTC)
✅ Reviewed your PR 7c0eaa7 Aug 09, 2026 · 13:30 13:31

@ai-coding-guardrails

Copy link
Copy Markdown

You've hit your review limit for the week, but don't worry you'll get some more next week!

Contact us at hello@zenable.io if you want this rate limit to go away

@codeant-ai

codeant-ai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@performance-testing-bot

Copy link
Copy Markdown

Unable to locate .performanceTestingBot config file

@coderabbitai

coderabbitai Bot commented Aug 9, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Required profile switches are now enabled and interactive. Their checked state can change and persist like optional profile switches.

Changes

Profile Switch Interaction

Layer / File(s) Summary
Enable required profile switches
lsposed-helper/app/src/main/java/com/sayanthrock/colorosthemes/lsposed/RootdSystemCustomizerActivity.java
Required profile switches are enabled instead of disabled, allowing their checked state to change and persist.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: enabling editing for all switches.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-editable-switches-13110576293345673495

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Aug 9, 2026
Comment on lines 192 to +193
option.setChecked(required || prefBool(key, defaultValue));
option.setEnabled(!required);
option.setEnabled(true);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Enabling switches marked as required lets the user turn them off, but the listener persists false while both initialization and rootdSystemReport() continue to force those profiles on via required || .... This creates a misleading UI and stores a state that the report and required-profile behavior ignore. Either make required profiles genuinely non-editable or remove the required override from initialization, reporting, and enforcement consistently. [api mismatch]

Severity Level: Major ⚠️
- ⚠️ Required switches display enabled after users disable them.
- ⚠️ Stored preferences disagree with required-profile UI state.
- ⚠️ Rootd support reports misrepresent required profile settings.

Fix in Cursor Fix in VSCode Claude

Prompt for AI Agent 🤖
This is a comment left during a code review.

**Path:** lsposed-helper/app/src/main/java/com/sayanthrock/colorosthemes/lsposed/RootdSystemCustomizerActivity.java
**Line:** 192:193
**Comment:**
	*Api Mismatch: Enabling switches marked as `required` lets the user turn them off, but the listener persists `false` while both initialization and `rootdSystemReport()` continue to force those profiles on via `required || ...`. This creates a misleading UI and stores a state that the report and required-profile behavior ignore. Either make required profiles genuinely non-editable or remove the required override from initialization, reporting, and enforcement consistently.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
👍 | 👎

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@lsposed-helper/app/src/main/java/com/sayanthrock/colorosthemes/lsposed/RootdSystemCustomizerActivity.java`:
- Line 193: Update the required-switch handling in RootdSystemCustomizerActivity
so rendering reads each switch’s saved preference value, using true only when no
value exists, instead of always forcing it enabled. Also update
rootdSystemReport() to read and report the persisted required-profile values
rather than always returning enabled.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4a0433d7-0e49-4105-8576-5fc86223895e

📥 Commits

Reviewing files that changed from the base of the PR and between 53e592e and 7c0eaa7.

📒 Files selected for processing (1)
  • lsposed-helper/app/src/main/java/com/sayanthrock/colorosthemes/lsposed/RootdSystemCustomizerActivity.java

Switch option = new Switch(this);
option.setChecked(required || prefBool(key, defaultValue));
option.setEnabled(!required);
option.setEnabled(true);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

Preserve the edited state of required switches.

Line 193 enables the control, but Line 192 still forces required switches to true whenever the activity renders. The listener saves false, but the next recreation ignores it. rootdSystemReport() at Line 229 also always reports required profiles as enabled. Read the preference directly and use true only as the default.

Proposed fix
-        option.setChecked(required || prefBool(key, defaultValue));
+        option.setChecked(prefBool(key, defaultValue));
...
-                    .append(required || prefBool(profile[0], true) ? "enabled" : "disabled")
+                    .append(prefBool(profile[0], true) ? "enabled" : "disabled")
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@lsposed-helper/app/src/main/java/com/sayanthrock/colorosthemes/lsposed/RootdSystemCustomizerActivity.java`
at line 193, Update the required-switch handling in
RootdSystemCustomizerActivity so rendering reads each switch’s saved preference
value, using true only when no value exists, instead of always forcing it
enabled. Also update rootdSystemReport() to read and report the persisted
required-profile values rather than always returning enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants