Repository navigation
Description
Issue Checklist
- I confirm that this feature request has not been previously suggested.
- I agree to follow the project's code of conduct.
- I have checked and verified that I am using the latest version of Code on the Go from GitHub or App Dev for All.
Additional terms
- I understand that feature requests are subject to evaluation and may not be implemented immediately.
- I agree to provide additional details if needed for a clearer understanding of the requested feature.
Feature description
Implementation of a lightweight "Pre-check" script that executes before the Gradle Daemon starts to optimize performance on mobile hardware.
Key Steps:
Sanitization: Automatically clears stale intermediate files/cache from the build directory to prevent "Ghost Errors."
Lightweight Validation: Performs a quick text-based syntax scan on .kt and .kts files for basic structural errors (unclosed brackets, missing imports).
The Gatekeeper: Halts the build process if errors are found, saving CPU cycles.
Addressing Vkrm's Feedback: To prevent lag on 32-bit/low-RAM devices, this scan will be a non-blocking background task focusing only on modified source files text (Incremental Scan). Cache clearing will be "Smart" (user-triggered or on failure) to avoid unnecessary re-compilations
Use Case
Resource Conservation on Low-End Hardware: This feature is highly beneficial for developers on 32-bit or low-memory devices. In mobile-based development, starting a heavy Gradle build—only to have it fail 5 minutes later due to a simple missing bracket—causes significant thermal throttling and battery drain. By catching these "doomed" builds in seconds via a lightweight text-scan, we save the device's CPU from unnecessary peak loads.
Benefits
Hardware Longevity: Reduces CPU stress and overheating on low-end devices.
Developer Productivity: Provides near-instant feedback on syntax errors.
Efficiency: Prevents the Gradle Daemon from locking up resources on builds that are guaranteed to fail.
Minimal I/O Overhead: Since the scan is restricted to source code text only, it respects the mobile's I/O limits compared to a full compiler run




Activity
coderabbitai commentedon Mar 26, 2026
🔗 Related PRs
#742 - ADFA-2308: force-stop tooling server upon shutdown [merged]
#934 - ADFA-2814 | Mitigate StrictMode disk I/O during APK install and quick build [merged]
#1011 - ADFA-3007 | Add proactive low storage check and dialog [merged]
#1018 - ADFA-3076 | Fix crash on unmapped modules during code actions [merged]
#1020 - fix/ADFA-680-685, 2037, 1103 Fix improper use of COGO, etc. in user-visible strings [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!