RikkaHub vs FoneClaw: Android Battery Task Setup
Set up RikkaHub Phone Use and FoneClaw's Android tools to read battery status, then open Battery Saver without toggling it. Compare permissions and evidence.
- RikkaHub Phone Use requires the GitHub edition on Android 11 or later, its accessibility service, and floating-chat overlay setup. The Play edition does not implement this route.
- FoneClaw separates a read-only battery-status query from opening Battery Saver settings. The settings tool opens an entry for manual control; it does not toggle Battery Saver.
- FoneClaw supports per-conversation model selection and requires HTTPS for compatible online endpoints, including LAN servers. Enabled tools, Android permissions, and active approval settings remain separate requirements.
- Compare actual battery results and the visible settings destination, not completion text alone. Keep the two requests separate, stop on uncertainty, and verify that no setting changed.
Two Routes for One Battery Task
A useful RikkaHub vs FoneClaw Android phone-control comparison starts with a bounded request: read the current battery level and power-saving state, then separately open the Battery Saver settings entry without changing its toggle. The first outcome is information; the second is navigation. Neither requires enabling power saving.
RikkaHub Phone Use can inspect and operate the Android interface under its prerequisites. In FoneClaw, we provide supported tools that separate the battery query from opening the relevant settings entry. This is a documented setup comparison and proposed reader procedure, not a report of hands-on tests or a speed ranking.
| Route | Setup focus | Execution and approval | Evidence to inspect |
|---|---|---|---|
| RikkaHub Phone Use | Supported GitHub edition, model, accessibility, and floating overlay | Observe the interface and navigate; distinguish model instructions from enforced guards | Current interface observations and the actual destination screen |
| FoneClaw Agent | Supported edition, conversation model, enabled tools, and active policy | Read battery state, then separately request the settings-opening tool under applicable approval | Returned battery data and the actual settings entry |
Keep the phone visible. A confident answer is not a substitute for a fresh result or an opened system screen.
Prepare the Edition, Permissions, and Model
RikkaHub's published Phone Use release provides phone operations as a shipped capability. Its platform and edition conditions require the GitHub edition on Android 11 or later. The Play edition has no Phone Use accessibility-service implementation. Prepare a compatible model connection, enable the RikkaHub Phone Use accessibility service in Android settings, and complete floating-chat setup with Android overlay permission.
For FoneClaw, first check the installed edition and whether both required tools are available and enabled. Our Download page distinguishes Full APK from Google Play Lite. These are distribution editions, not membership levels. Lite supports the plugin marketplace, scheduled tasks, and shortcuts within its available tools; that does not establish identical per-tool coverage. Plugins run within Agent.
We offer a free default model as a starting option, or you can configure compatible API access. Models can be selected per conversation, so inspect the active model for this task. FoneClaw requires HTTPS for online model endpoints, including servers on your LAN. That connection rule is specific to FoneClaw, not a requirement to impose on every other client.
Finally, separate model compatibility from device authority. A successful text response does not establish tool support, Android permission, or approval to execute. Review the actual tool configuration and policy before making either request.
Use RikkaHub to Inspect the Android Interface
RikkaHub's Phone Use tool instructions point to the app's notification settings for floating-window setup, followed by the Android overlay grant. The floating window lets you watch and stop operations. The tool cannot operate RikkaHub's own foreground interface: its workflow starts by opening another app or going home, then observing the visible screen.
After completing setup, use a narrowly worded first request:
Open Android settings if needed. Read the current battery level and whether power saving is enabled. Do not change any setting. Report only what you can establish, then stop.
This asks for inspection, not optimization. If the relevant state is not exposed, the useful result is an explicit limitation rather than a guessed percentage or an assumed on/off state.
Phone Use prefers visible accessibility elements. Actions should use the latest observed element indices; those references can change when the screen changes. A screenshot is a fallback when the element list is insufficient, not a requirement for every operation. If screenshot interpretation becomes necessary, check the selected model's image support separately.
Review the first result before issuing the second request:
Open the Battery Saver or equivalent power-saving settings entry. Do not toggle anything, accept a change, or enable a mode. Leave the entry visible for me to inspect, then stop. If the destination is unclear, ask me.
Manufacturers organize battery settings differently. Inspect the actual page and its current switch state; do not expect one universal screen title or tap sequence. For this exercise, reaching the appropriate entry without changing its state is the intended navigation outcome.
Use FoneClaw's Scoped Battery Tools
In FoneClaw, we separate these requests through two supported tools. The battery-status tool, device_battery_status, returns read-only Android battery and power-saving information. The Battery Saver settings-opening tool navigates to the system entry. Our Features page explains the supported-tools approach and approval controls.
Start with the query alone:
Read my current battery level and power-saving state using the supported battery-status tool. Do not change settings or open another screen. Report the returned state, then stop.
Inspect the actual tool result rather than accepting a model's unsupported estimate. The query does not change settings. Its normally low-risk handling remains subject to your global approval mode and any per-tool overrides; do not assume that the same authorization behavior applies to every installation.
Only after reviewing that result, make the separate navigation request:
Open the Android Battery Saver settings entry using the supported settings tool. Do not enable or disable Battery Saver. Leave the screen for me to review, then stop.
Opening this entry is device control and is subject to the applicable approval requirement under your active policy. Review any requested authorization before allowing execution. On some vendor versions of Android, the destination may fall back to general battery settings instead of a dedicated Battery Saver page.
The settings-opening tool does not directly toggle Battery Saver through the public Android API. Enabling or disabling it remains a manual user action after the entry opens. In this exercise, leave it unchanged. Record whether the specific entry or a fallback page appeared; an opened settings page is not evidence that power saving was enabled, disabled, or otherwise changed.
Understand Approval, Visibility, and Stopping
RikkaHub's Phone Use safeguards include code restrictions for a finite list of named payment and banking packages. That is not a guarantee covering every financial app. Its model instructions also say to stop and ask before paying, sending, or deleting unless the user already explicitly requested that exact action. A model instruction is different from an enforced confirmation dialog before every irreversible step.
In FoneClaw, global approval settings and per-tool overrides govern actual calls. Android permissions provide the underlying authority, while tool availability and approval policy determine how a requested operation proceeds. Granting a permission does not by itself express consent to every possible future action.
For the battery exercise, keep authorization narrow: a read-only query first, followed by a separate request to open an entry. If either app proposes toggling power saving, the request has exceeded the intended scope. Stop and inspect the current state before continuing.
With RikkaHub, use the floating window to watch and stop the operation; revoke its accessibility or overlay access in Android settings when you no longer want that authority available. In FoneClaw, stop the current task and disable tools you do not need. Use the stop controls available in your installed edition; labels may vary.
Stopping prevents further work as applicable; it does not undo an action already completed. Check the phone afterward rather than assuming cancellation restored its previous screen or settings.
Find the Failing Step Before Retrying
Diagnose the first missing prerequisite or failed outcome. Changing the model, granting more permissions, and repeating the whole request at once makes it harder to identify what was wrong.
| Symptom | Check first | Next step |
|---|---|---|
| RikkaHub Phone Use is unavailable | GitHub edition and Android version, then accessibility service and floating overlay | Correct the missing prerequisite rather than assuming ordinary chat has phone authority |
| RikkaHub targets an outdated screen element | Whether the interface changed after observation | Observe again and use the current element list |
| A custom view exposes insufficient text | Accessibility observation and conditional screenshot support | Use a screenshot only where needed and supported by the model, or inspect manually |
| FoneClaw reads battery state but cannot open settings | Availability of the separate settings tool, active approval, Android authority, and vendor destination | Inspect any pending authorization or reported fallback before retrying |
| FoneClaw's model request fails before a tool runs | Conversation model, provider configuration, HTTPS endpoint, and network access | Repair the connection separately from device permissions |
| The reply says complete but the destination is unclear | Actual screen and execution state | Stop, inspect manually, and record the navigation as unverified |
If general battery settings appear, do not silently count that as reaching the exact requested entry. Note the fallback and decide whether manual navigation is appropriate. Never respond to uncertainty by letting the agent search through unrelated settings or change a toggle.
Before sharing diagnostic screenshots, remove API credentials and unrelated private screen content. A useful report identifies the failed stage without exposing the rest of your phone.
Record Evidence and Costs Separately
Use this worksheet on your own device, keeping the task boundaries the same for both routes. Record the time and charging condition: battery values can change between attempts, so identical percentages are not a sensible acceptance requirement.
- Environment: Android version, app edition, selected model, relevant enabled tools, and granted permissions.
- Query evidence: The returned or observed battery state, its source, and anything the route could not establish.
- Navigation evidence: The actual destination, whether it was a dedicated entry or fallback, and confirmation that the toggle remained unchanged.
- Authorization: Any approval requested, pending state, or policy condition that affected execution.
- Stopping and recovery: Whether you stopped the task, what remained visible, and what required manual inspection.
- Costs: The active model service and applicable usage charges, kept separate from app plans or distribution editions.
Keep the record minimal; a short description of the result is often enough. Do not fill missing observations with assumed successes or numerical scores.
Our free default model and an optional custom provider are different service arrangements. Check the selected provider's billing and processing terms when using your own API. Local interface operations do not establish local-only model inference or private on-device storage of every request.
Choose the Route You Can Verify
Choose RikkaHub Phone Use when its supported edition, accessibility setup, and visible screen-operation workflow fit the task you want to supervise. Choose FoneClaw when our available tools express the operation you need and their permission and approval boundaries fit your requirements. Neither choice follows from model reputation alone.
For broader client selection, read Best BYOK AI Assistants for Android: Four Clients Compared. If you need custom provider configuration, Connect an AI Model API to FoneClaw: Text, Images, and Android Tools covers connection fields and separate compatibility checks.
Start with the read-only battery query. Inspect its evidence, then request the settings entry separately and leave its toggle untouched. The useful comparison is whether you can configure the route, understand its authority, and verify the outcome before expanding the task.