Do I need to update every time?

Use the newest available APK when Spark screens change, Android permissions behave differently, or support asks you to update during setup.

Where should I download LumosWS?

Download only from getlumos.app or from the official support flow. Avoid APK files sent directly in chats or reposted by other people.

Does an update change my Spark account?

No. LumosWS runs locally on Android and does not ask for a Spark login. Spark stays inside the official Spark app on your phone.

LumosWS changelog and release notes

Latest public update

The current public update is centered on reliability and clearer setup rather than new promises. It keeps LumosWS aligned with the way Spark offer screens, queue states, and Android install behavior can change over time.

Spark screen changes: refreshed checks for visible offer cards, action buttons, and states that can appear before or after an offer opens.
Queue checks: stronger handling when several offers are visible or partially hidden, so the first card is not treated as the only option by default.
Stability: fixes around stale trip state, timing, repeated checks, and cases where an old state could block new offer review.
Install flow: clearer APK install guidance for restricted settings, Accessibility access, Notification access, and official download paths.
Security hardening: tighter account boundaries, release checks, license checks, and reminders to avoid APKs from chats or unofficial mirrors.

Updates for Spark screen changes

Spark can adjust labels, screens, offer cards, modals, and queue behavior. LumosWS updates are meant to keep reading and tapping tied to what is actually visible on the Android screen, not to a blind script.

Boundary: LumosWS does not log in to Spark, call Spark servers, or change a Spark account. It reacts to the local Android screen and permissions that the driver can turn off.

Stability and queue checks

Recent work has focused on practical shift conditions: offers arriving while another state is still settling, queues with more than one card, and screens that need another check after scrolling or waiting.

Re-check visible offer state before an action when the screen is still moving.
Handle multi-offer queues more carefully when better value may sit below the first visible card.
Avoid relying on stale state when Spark is slow to update trip or offer status.
Keep history useful so accepted, skipped, and seen offers can be reviewed after a shift.

Install and update flow

LumosWS is distributed as a direct Android APK, so the install flow needs to be clear. The install guide explains browser downloads, restricted settings, Accessibility access, Notification access, and what to check before a real shift.

Install: Use the Android install guide and download only from getlumos.app. Do not install APK files sent through chats, groups, or mirrors.

Security and account boundary

Security updates are focused on reducing unnecessary trust. LumosWS should not need a Spark username, Spark password, bank login, card number, or shared cloud Spark session to run on a driver's phone.

Keep Spark credentials inside the official Spark app.
Use visible Android permissions that can be revoked in Settings.
Use the official Telegram bot only for license access and support.
Keep the public download path and release checks aligned so drivers know where updates come from.

Support: Use the official Telegram bot for license or setup help.

What release notes do not mean

Updates improve the app, but they do not create Spark orders, guarantee earnings, guarantee hidden offers, promise account outcomes, or make every phone and market behave the same way. Test the trial on your own Android phone before relying on any setup during busy hours.

Important: LumosWS is not affiliated with, endorsed by, or approved by Spark. Drivers remain responsible for their own account choices, filters, and platform risk.