JARVIS v2.5.6 RC1

JARVIS 2.5.6 RC1 brings the updated Android interface and shortcut setup.

• Cleaner home screen: removed the local-features banner and restored Capabilities in the bottom navigation.
• Personal shortcut bar: choose any of the available controls, reorder them, show labels, and swipe when they do not all fit.
• First-launch introduction: learn what each button does, then pick your shortcuts. Replay it from Settings → Interface → Edit top bar.
• Updated reading, step-by-step activities and gesture controls, including bookmarks, focused practice, action editing and clearer session controls.
• Preferences remain saved on the device, and the bottom navigation stays visible on narrow screens.

Install the attached arm64 APK on Android 7.0 or newer. This is a release candidate; physical-device acceptance and foundation promotion remain pending. The stable release channel is unchanged.

Validation: 753 tests passed, 9 live-provider tests skipped, 10 protocol fixtures passed, and all 3 release-gate regression tests passed. TypeScript, lint, the web build, signed APK packaging and native regression tests passed in release CI.

The downloadable APK was verified as com.jarvis.app, version 2.5.6-rc.1, ARM64, with the same signing certificate as the published v2.5.0 APK. Its embedded frontend bundle identifiers match the tagged source and CI build. A SHA-256 checksum is attached alongside the APK.

JARVIS v2.5.0 — Iron Man mode, specialist agents & a connected home

A new look. Specialist agents. One memory across your phone and PC.

JARVIS v2.5.0 brings the desktop's interface to Android, including Iron Man mode, and adds agents you can choose for research, files, scheduling, content and device control. Your phone and PC can share memories and routines, your TV gains visual control and media handoff, and coming home can trigger a routine notification.

Everything below is new or improved since v2.4.0.

Download

Download JARVIS-v2.5.0-arm64.apk · 34.3 MB · Android 7.0+ · 64-bit ARM

See the README for setup. PC features use the paired JARVIS for Windows app; use a matching update for the new cross-device features.

A completely rebuilt interface, including Iron Man mode

• The desktop's home screen, adapted for your phone. A greeting clock, animated centrepiece, quick controls, live status, your last reply, an ask box, starter prompts and useful cards. Chat, Memory, Skills and Capabilities sit in the bottom navigation around the mic.
• Modern and Iron Man presets. Keep the animated orb and clean cards, or switch to the arc reactor, HUD typography, ring gauges, sharper corners and stronger glow. Try “Switch to Iron Man mode.”
• Make it yours. Change colours, fonts, card styles, gauges, glow, corners and spacing. Choose a grid, aurora, minimal or solid background, or use your own picture. Show, hide and reorder cards, save your own themes, and import theme files.
• Find things faster. A new command palette opens from the header search. Settings are grouped and searchable, with an Interface page; Memory, recent chats and Capabilities also have search.
• Better chat. Agent handoffs have their own cards, replies have a copy button, and Markdown tables render as readable, horizontally scrollable tables.
• Photos in the conversation. Attach a photo or screenshot and ask JARVIS about it. Images are resized before being sent to the configured model.

Pick an agent for the job

Use the agent row on the home screen or in chat, type a handle such as @files, or say “Tell the research agent to…”. Leave it on Auto to let JARVIS choose its tools.

Agent	What it handles
Phone	Apps, device controls, messages and calls on this phone.
Research	Web searches, reading sources, comparisons and answers with links.
Files	Listing, reading and summarising text files in the folder you grant access to.
Scheduler	Alarms, timers, reminders, agenda items and routines.
Content	Drafting posts, messages and documents, plus image generation with a supported provider.
Desktop	Windows apps on your paired PC.
Browser	Websites in your paired PC's browser, including its signed-in sessions.

Research now runs directly on the phone, even when a PC is paired. It can search from several angles, open public pages, compare findings and cite its sources. A PC no longer needs to be online for this workflow. Pages requiring JavaScript, login or anti-bot checks may need an alternative source.

When work goes to the PC, handoffs, questions and returned findings appear in the chat. For larger requests, JARVIS can also consult a specialist for information or a draft while keeping the main conversation together.

One memory across your phone and PC

• Remember it once. Saved facts and routines sync over the paired connection. Tell JARVIS on either device, and the other can pick it up when connected.
• Forget it on either device. Deletions sync too, and the memory digest now takes forgotten facts into account.
• Routines keep their home. A synced timed routine still runs on the device where you created it.
• Nightly memory digest. Once a day, at the first idle moment when JARVIS is open after 03:00, it reviews your own messages and saves up to five new facts worth remembering. Review or delete them in Memory, or turn the digest off under Memory → About you.

“When I get home” routines

Try “When I get home, turn on the TV and play lofi.” JARVIS learns your home Wi-Fi from where your paired TV or PC answers, then posts a notification when you return. Tap the notification to run the routine. No location permission is needed.

Home-network detection now works while Tailscale is connected, and brief Wi-Fi dropouts are filtered out. Arrival detection and routine-notification handling also received fixes from real-device testing.

More ways to control your TV and wake your PC

• TV by sight. Ask “What's on my TV?”, or give a visual task such as “On YouTube, play the second result for lofi.” JARVIS can inspect the screen between remote-control steps. Netflix and other protected screens block screenshots.
• Send what's playing to the TV. “Send this to the TV” adds handoff for supported YouTube and Netflix playback. YouTube uses the detected playback position; Netflix uses its saved resume point. The handoff also pauses playback on the phone and requires notification access.
• Share a link to JARVIS. Send a YouTube or Netflix link from another app's Android Share menu to play it on the TV. YouTube links can carry a start timestamp.
• Wake your TV or PC. Wake-on-LAN support adds “Turn on my PC” and waking a supported TV with Remote Start enabled. The phone must be on the same home network, and the target device needs wake support enabled.
• Better TV connections. Multiple saved addresses, including a Tailscale address, help with homes that have separate router networks. Unreachable TVs produce clearer results.
• More reliable playback. Fixes cover YouTube playback checks, repeated pause commands, TVs in standby, Netflix season IDs and named episodes. Netflix success now also requires Netflix to remain in the foreground.

Requests can reach your phone from the PC and WhatsApp

Ask at the PC, act on the phone. Say “Set an alarm on my phone” at your paired PC, or send that request through the PC's WhatsApp integration. The phone performs the supported action and reports back. This covers alarms, timers, reminders, device switches, volume and music. Enable it under Settings → PC & WhatsApp; JARVIS needs to be open or recently used on the phone.

WhatsApp replies from the phone, with the PC offline. Listed contacts can send messages beginning with “Jarvis”, and JARVIS can answer through WhatsApp's notification reply action. Choose Off, When my PC is offline or Always, and specify the contacts allowed to use it. Notification access is required. If Android has suspended the app, a tap-to-run notification brings the request back into JARVIS.

Phone-side WhatsApp is experimental and still needs an end-to-end device test. WhatsApp's “Message yourself” chat does not generate the notifications this feature needs; using it from your own number requires a separate WhatsApp number for JARVIS.

Faster answers and more dependable actions

• Weather without the extra wait. Plain local weather requests now return the actual tool answer directly, with no model calls. Recorded device checks took roughly 1–2 seconds.
• Instant notification reads. Plain local notification requests use the native reader directly, redact verification codes and return the text without sending notification bodies to a model. The recorded sample completed in 174 ms.
• Less unnecessary review. Simple single-tool requests use their actual result. Complex requests and turns with multiple tools retain completion review; phone-action verification and approvals still apply.
• Lighter model requests. Only relevant tool groups are loaded initially, with additional groups available as needed. Automatic model fallback continues without repeated model-switch popups.
• STOP works across turns. Cancelling a task no longer leaves later requests stuck in a stopped state.
• Camera tasks check saved media. JARVIS verifies that a photo or video was actually saved. A phone task that already acted and then failed is no longer silently retried with reworded instructions in the same turn.
• Clearer results. Research and Files answers survive reviewer outages with an explicit unverified note; charts and drafts avoid false action warnings; unsaved calendar drafts are described as needing Save; hardware queries use the actual Android model identifier.
• Timer and Spotify fixes. Running timers can be cancelled through the Clock app's verified notification action. Failed Spotify search playback can continue through the phone operator and verify the resulting track.
• Steadier remote PC control. Reconnect acknowledgements preserve the control countdown, stale video is cleared, stream recovery is bounded, and Android Back closes live view cleanly.
• Recorded progress for complex work. Interrupted conversations retain completed results and pending work without automatically replaying actions.

Validation and remaining limits

Recorded release validation: 522 TypeScript tests passed, 9 skipped; 148 native tests passed, plus typecheck, lint and web/native APK builds. Real-device checks covered weather, notification reading, STOP, timer cancellation, Files, Spotify fallback, remote video and Back, and TV playback, visual search, standby/wake and Netflix episode controls.

The positive phone-current-video → TV handoff still needs an end-to-end device test. Places lookup can still fail when its public map services time out. Some new interface flows were checked in a browser or emulator rather than on a phone, and Android background limits still affect when incoming requests can run.

See the release's detailed status and [device...

JARVIS for Android v2.4.0: one-step phone actions, WhatsApp messages and calls

Things Gemini does in one step, JARVIS now does in one step too: WhatsApp messages and calls, the flashlight, Do Not Disturb, your notifications and more.

⚠️ Experimental. Read SECURITY.md before giving it control of your phone or PC.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v2.3.0 without losing your settings, your routines or your PC pairing. Setup steps are in the README.

What's new since v2.3.0

• One-step phone controls. "Turn on the flashlight", "turn on Do Not Disturb", "pause the music", "next song", "volume up", "set brightness to 30%", "turn on auto-rotate", "lock the screen". JARVIS now does these directly, instead of driving Quick Settings step by step. It reports what the phone actually ended up in, not what it asked for.
• WhatsApp messages and calls by contact name. "Message Mom on WhatsApp: on my way", "call Dad on WhatsApp". JARVIS finds the contact and shows you exactly who, which number and what text, and only sends after you tap Allow. If a WhatsApp notification from that person is showing, the reply goes out through the notification and WhatsApp never opens. Otherwise WhatsApp is on screen for a couple of seconds while JARVIS presses Send, then JARVIS comes back. Texts (SMS) and phone calls work the same way.
• Your notifications. "What are my notifications?" reads what's showing. Verification codes are hidden before the AI model sees them.
• Navigation. "Navigate to …" starts Google Maps turn-by-turn directions directly.
• Permissions only when needed. The first time a feature needs one, JARVIS asks for Contacts, SMS or Phone. For Do Not Disturb access, Modify system settings and Notification access, it opens the right Settings screen for you to switch it on. If Android greys out Notification access as a "restricted setting", go to App info ▸ ⋮ ▸ Allow restricted settings, then try again.
• Honest about what Android won't allow.
  • On Android 15 and later, an app can only turn off a Do Not Disturb it turned on itself. For one you started, JARVIS says so and hands it to the step-by-step operator, which can switch it off in Quick Settings.
  • Spotify doesn't accept play requests from other apps, so "play … on Spotify" still goes through the step-by-step operator.
  • Apps paused by parental controls or Digital Wellbeing are reported as paused, instead of JARVIS claiming it opened them.
  • Wi-Fi, Bluetooth, mobile data and airplane mode can't be switched by any app, so those also still go through the operator.
• Fixes:
  • "Show my alarms", "show my timers", "dismiss the timer" and asking for calendar access didn't work, because the app left out values the native side requires.
  • JARVIS no longer answers "OK", "I've sent it" or "routing you there" without doing the action. It now catches itself and actually does it.

Known issues

• SMS and ordinary phone calls haven't been tested on a phone with a SIM card yet. WhatsApp video calls, the lock-screen command, and play/pause/skip while music is playing are also still untested on a phone.
• "Play … on Spotify" is slower than the other one-step actions, because it goes through the step-by-step operator.
• The screenshot in the README still shows an old home screen.
• Carried over: force-stopping JARVIS from App info makes Android switch off its accessibility service, and the app is signed with a development key.

JARVIS for Android v2.3.0: a home screen that tells you what works, and routines you can see

A home screen that tells you what works, and routines you can see, edit and get reminded of.

⚠️ Experimental. Read SECURITY.md before giving it control of your phone or PC.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v2.2.1 without losing your settings, your routines or your PC pairing. Setup steps are in the README.

What's new since v2.2.1

• A Status card on the home screen. It shows whether the wake word is on, whether app control (the accessibility service) is allowed, which model is in use, and whether your PC and TV are connected. Anything that needs attention turns amber, and tapping a row takes you to where it's fixed.
• A Routines card. Every saved routine is listed with when it runs ("Every day at 08:00", "When you ask"). Run one with a tap, see its steps, add a new one or edit one in a short form, or remove it.
• Timed routines run while JARVIS is closed. At the routine's time JARVIS posts a notification; tap it and the routine runs. Alarms are re-set after a reboot and follow a time-zone change. An untapped notification doesn't count as a run.
• A calmer home screen. One row of tabs at the bottom instead of three, the live status in the top bar, and the panels as plain cards: Device (memory, storage), Battery (level, charging, real temperature), Agenda, Weather (line icons that match the current conditions), Network (connection, with speed marked as an estimate) and the action log.
• Every menu looks and works the same. Customize, Remote PC & TV, Tasks and Memory now use the same full-screen design as Settings, and Android's back button closes each of them instead of leaving the app.
• Chat has a mic button when the box is empty and suggested first questions. A routine run shows as "Run name" instead of its internal instructions.
• Fixes: recovered phone tasks show what they were doing instead of "Recovered phone task"; the receipt hash in Tasks is folded under Details; Customize's move and reset buttons work on the phone; "move the weather panel up" by voice works; "reset my home screen" by voice redraws it straight away; wind is in km/h unless your region uses mph; the agenda's add and edit happen in the card instead of pop-up dialogs.

Known issues

• The first tap on a routine notification may only expand the notification group on some Samsung phones; tap it again to run the routine.
• A fix for the app closing when the system font size or style changes was checked on the emulator, not yet on a phone.
• The screenshot in the README still shows the old home screen.
• Carried over: force-stopping JARVIS from App info makes Android switch off its accessibility service; the app is signed with a development key.

JARVIS for Android v2.2.1: Netflix on the TV works again

"Play Stranger Things on the TV" works again. Netflix changed its title pages and JARVIS stopped recognising which show it had found.

⚠️ Experimental. Read SECURITY.md before giving it control of your phone or PC.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v2.2.0 without losing your settings or your PC pairing. Setup steps are in the README.

What's new since v2.2.0

• Netflix shows play on the TV again. JARVIS checks a show's name against its public Netflix page before playing it. Netflix's pages no longer carry the name in the page title, and seasons are now listed differently, so the check found nothing and "play show on the TV" (and "season N episode M") failed. JARVIS now reads the new layout and still understands the old one. Checked against netflix.com with Stranger Things (S1E1, S5E8), Dark (S3E8) and Red Notice.

Known issues

• The Netflix fix was checked against netflix.com from a PC, not yet end to end from a phone to a TV.
• Carried over: force-stopping JARVIS from App info makes Android switch off its accessibility service; the app is signed with a development key.

JARVIS for Android v2.2.0: say it in one breath

"Hey Jarvis, open YouTube" in one breath now works. Before, the first word or two after "Hey Jarvis" were lost if you didn't pause.

⚠️ Experimental. Read SECURITY.md before giving it control of your phone or PC.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v2.1.0 without losing your settings or your PC pairing. Setup steps are in the README.

What's new since v2.1.0

• Commands said in one breath keep their first words. After "Hey Jarvis", the app used to switch from the wake-word microphone to a second one for your command, and anything said during that ~0.5–1 second switch was lost: "Hey Jarvis, what is five plus five?" arrived as "That's five." The wake-word listener now records the command itself, so nothing is lost. A pause after "Hey Jarvis" still works too.
• One speech-to-text call per command instead of two. The wake and the command are sent as one recording, which also does the check that you really said "Hey Jarvis". Saying "Hey Jarvis" and then nothing sends nothing.
• JARVIS tells you when there's an update. Once a day at most, it asks GitHub for the latest release and shows "JARVIS x.y.z is available — Get it" when there's a newer one. Get it opens this page; the app never installs anything itself. GitHub sees your IP address when it checks; nothing else is sent.

Known issues

• If the speech-to-text call fails (no network, rate limit), the command is dropped with an error. Before, a separate recording could still go through.
• In a noisy room a command can take up to about 10 seconds to be sent, because the app waits for a pause.
• Carried over: force-stopping JARVIS from App info makes Android switch off its accessibility service; the app is signed with a development key.

JARVIS for Android v2.1.0: web search with a backup

Web search keeps working when Gemini can't answer. Add a free Tavily key and searches fall back to it when every Gemini key is rate-limited, or when you have no Gemini key at all.

The Windows version is now open source: AnaaySampat/jarvis-windows

⚠️ Experimental. Read SECURITY.md before giving it control of your phone or PC.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v2.0.0 without losing your settings or your PC pairing. Setup steps are in the README.

What's new since v2.0.0

• A backup for web search. Web search runs on Gemini, and it shares the same daily quota as chat and phone tasks. When that quota ran out, searches just failed. You can now add a Tavily key in Settings ▸ API keys ▸ Web search backup. Gemini is still tried first; Tavily answers only when Gemini can't. If both fail, JARVIS says so. The key is stored encrypted on the phone like your other keys.
• No phantom commands after a wake with nothing said. If you said "Hey Jarvis" and then nothing, the silence still went to the speech recogniser, which sometimes made up a command. Silent captures are now dropped before they're sent.

Known issues

• Both changes are unit-tested but haven't been run on a phone yet.
• Carried over: "Hey Jarvis, open X" in one breath can lose the first word or two; force-stopping JARVIS from App info makes Android switch off its accessibility service; the app is signed with a development key.

JARVIS for Android v2.0.0: a steadier link to your PC

A steadier link to your PC. The phone now notices a dead connection, reconnects on its own, and gets back task results it missed.

The PC version has now been Open sourced! https://github.com/AnaaySampat/jarvis-windows check it out!

⚠️ Experimental. Read SECURITY.md before giving it control of your phone or PC.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v0.1.5 without losing your settings or your PC pairing. Setup steps are in the README.

What's new since v0.1.5

• Dead connections get noticed. After switching between Wi-Fi and mobile data, the PC link could keep showing "online" for minutes while anything you sent went nowhere. The PC now sends a signed keepalive every 20 seconds. If the phone hears nothing for 50 seconds, it drops the link and redials.
• Faster reconnects. Coming back to the app, getting signal back, or changing network type now redials straight away, instead of waiting out a retry timer of up to 15 seconds.
• Results aren't lost. If the link dropped during a PC task (say the phone locked) and came back after the task ended, the phone never got the result and later blamed the PC for "no progress". It now receives the result when it reconnects. A task re-sent after a dropped link is no longer run twice.
• "PC busy" actually arrives. A task sent while the PC was busy used to vanish. You'd hear nothing for about 3.5 minutes, then a wrong message. Now you're told straight away.
• The live screen comes back by itself after a reconnect. Before, the PC could refuse your own phone's screen as "another device" for up to 40 seconds after a network switch.
• Sharper, smoother live screen. Text is properly smoothed instead of losing whole rows of pixels, and the PC keeps up its frame rate.
• Dragging keeps up. Each move has to be signed on the phone, so a long drag queued moves faster than they could be sent and the cursor fell further and further behind your finger. Only the newest position is sent now.
• The phone waits up to 20 seconds for the PC link before giving up on a task, so a task right after opening the app no longer fails while the link is still starting.

Known issues

• The keepalive, the result replay, the "busy" message, the screen takeover and the sharper screen need the matching update of the Windows desktop app. With an older desktop app, this version works as before; it just doesn't get those fixes.
• The live screen tops out around 15 fps on a 1080p PC; capturing the screen is the slow part.
• The jump to 2.0.0 is a version number change only; nothing was rewritten.
• Carried over: "Hey Jarvis, open X" in one breath can lose the first word or two; force-stopping JARVIS from App info makes Android switch off its accessibility service; the app is signed with a development key.

JARVIS for Android v0.1.5: control your TV by voice

Control your TV by voice from your phone. Tested on a real phone and TV.

⚠️ Experimental. Read SECURITY.md before giving it control of your phone. TV control works through your TV's USB debugging, which gives an approved device full control of the TV.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v0.1.4 without losing your settings. Setup steps are in the README.

What's new since v0.1.4

• TV control. Say "open Netflix on the TV", "play Stranger Things on the TV", "play Stranger Things season 1 episode 1 on the TV", "pause the TV", "set the TV volume to 20" or "turn the TV off". The phone talks to an Android TV on the same Wi-Fi through the TV's own USB debugging, so nothing gets installed on the TV. Before saying something worked, JARVIS checks with the TV itself: which app is in front, the volume level, whether Netflix is really playing. Plain remote-button presses ("press down 3 times") are reported as sent, because the TV can't confirm them.

  Setup: on the TV, go to Settings → Device Preferences → About and click Build 7 times, then turn on USB debugging in Developer options. In JARVIS, open the Remote PC & TV screen (the monitor button), type the TV's IP address (Settings → Network on the TV), tap Connect, and accept "Allow USB debugging?" on the TV (tick Always allow).

  Tested with a Samsung Galaxy phone and a Sony KD-55X8500D (Android TV 8): connecting, opening YouTube, setting the volume, playing a show on Netflix, pausing and resuming.

• JARVIS won't claim it did something it didn't. "Resume" got the reply "Resumed" (naming a different show) while nothing reached the TV. The AI's answer is now checked for media words like that, and an unbacked claim is sent back to actually do it.

• Routines (not yet tested on a phone): "save a morning routine: give me the weather, today's agenda and top news", "run my morning routine", or the same at a set time ("every weekday at 8"). Timed routines only run while JARVIS is open.

Known issues

• JARVIS can't see the TV screen. Sony's screenshots come back black, and Netflix, YouTube and Prime Video don't expose their screens. So inside apps, beyond playing and pausing, it can only press remote buttons, without confirmation.
• "Play <show>" resumes wherever the active Netflix profile left off. In testing it resumed Season 5 on a profile that was on Season 1; we don't know why yet. Name the season and episode to pick one. Episode links are new and not yet confirmed on a TV.
• After a cold start Netflix asks "Who's watching?"; JARVIS picks the highlighted (last-used) profile.
• "Play <something> on YouTube" opens YouTube's search and plays the top result. Not yet confirmed on a TV.
• The phone and TV must be on the same Wi-Fi. If you stop using this, turn off USB debugging on the TV.
• Carried over: "Hey Jarvis, open X" in one breath can lose the first word or two; force-stopping JARVIS from App info makes Android switch off its accessibility service; the app is signed with a development key.

JARVIS for Android v0.1.4: the wake word stops answering conversations

"Hey Jarvis" stops answering conversations, and web search works on free Gemini keys. Tested on a real phone.

⚠️ Experimental. Read SECURITY.md before giving it control of your phone.

Download

File	Use it for
jarvis-release.apk (34 MB)	Installing and using the app.

64-bit ARM phones (every modern Android phone), Android 7.0+. Installs over v0.1.3 without losing your settings. Setup steps are in the README.

What's new since v0.1.3

• The wake word ignores conversation about Jarvis. The on-device model alone would start a command whenever someone nearby said something close to "Hey Jarvis", including just talking about JARVIS. Now each wake is double-checked: the speech recogniser must also hear "Hey Jarvis" in the few seconds that triggered it. Measured on a real phone with this build: 16 of 16 real "Hey Jarvis" commands ran, and the wake model fired on 7 sentences about Jarvis ("Jarvis is the name of the assistant in the Iron Man movies", "Say hey to Jarvis for me", "Hey, did Jarvis finish the task?") — all 7 were ignored, where v0.1.3 would have sent each one to the AI as a command.

  Say "Hey Jarvis": a bare "Jarvis, …" is now ignored on purpose. The check adds no wait: it runs while you're still speaking.

• Web search works on free Gemini keys. Google only allows search on Gemini 2.5 models on the free tier, and JARVIS used to search with whichever Gemini model was selected (a newer one by default), so every search failed there. Search now uses Gemini 2.5 Flash, then Flash-Lite, and tries each of your Gemini keys. It keeps working when chat has fallen back to Groq: asked about the latest Formula 1 race, it found the one from the day before.

• Steadier answers on backup models. Questions like "what model is my phone?" or "what's my battery at?" are now looked up on the phone instead of answered from memory (it used to need the words "on my phone"), and the AI is told today's date, so "how many days until New Year's?" comes out right.

Known issues

• "Hey Jarvis, open X" in one breath can still lose the first word or two of the command ("what is five plus five" arrived as "five"). Pause after the beep. The fix, recording the command natively, is next.
• The wake check needs the internet. When the phone is offline it lets every wake through, as before.
• Anyone who says "Hey Jarvis" can still wake it; this is not voice recognition.
• Force-stopping JARVIS from App info makes Android switch off its accessibility service. Re-enable it in Settings → Accessibility.
• Signed with a development key. A future build signed with the final key may need you to uninstall first, which clears the app's data.