BandSight — Source library
Public documentation snapshot: 2026-09-08
Start a receive-only session
Use a compatible RTL2832U receiver with an R820T2/R860-family tuner, a suitable antenna and an Android device that supports USB Host/OTG. A phone alone does not provide this SDR receiver. Connect through a data-capable OTG adapter or suitable powered hub, open BandSight and approve Android’s USB access request for the receiver you recognize. Check the hardware status before starting. Choose Manual, Scan or ISM decode, confirm the frequency and mode, then start the intended operation. First test a known public reference signal that you are allowed to receive. Stop receiving or recording before unplugging the dongle. BandSight never transmits, replays signals, unlocks devices or jams a frequency. Reception and sharing still require authorization under applicable rules.
USB connection and permissions
Use a cable that carries data, not a charge-only cable. The phone must support USB Host/OTG. A receiver draws power; some phones need a powered hub or a different adapter. Approve the system USB permission prompt only for the connected receiver you intend to use. If you cancel, reception stays unavailable until you grant access. Unplugging invalidates the current receiver connection. Only one application can claim the receiver interface at a time. If another app or browser tab holds it, stop and close that receiver session before reconnecting here. The browser edition uses WebUSB when supported. A Windows browser may also require an appropriate USB driver; that is separate from Android’s native USB Host permission. The hardware guide explains the platform differences.
Fix missing hardware or an empty result
No receiver: check OTG support, the data cable, power and the USB prompt. Interface busy: close the other app holding the dongle. A permission denial or disconnected cable is not evidence that no signal exists. Flat spectrum or silence: check the antenna, frequency units, tuning mode, volume and whether a known reference signal is available locally. A strong signal can overload a receiver; an unsuitable antenna can miss one. If reception stops during a recording, inspect the completion or error message and verify the saved file before sharing it. For a storage error, keep the original data and free space without deleting the affected collection. For help, use support@autosecurelogin.com. Include the app version, Android version, receiver model, adapter, operation and a redacted error. Do not send private recordings, device identifiers or sensitive location data unless necessary and deliberately chosen.
Manual tuning and audio modes
In Manual mode, enter the frequency and select the displayed unit before tuning. A value in MHz is different from the same number in kHz. Confirm the resulting frequency in the receiver display. Use WFM for compatible wideband FM broadcast, NFM for compatible narrowband FM, or AM for compatible amplitude-modulated audio. A visible carrier does not mean every mode will produce intelligible audio. The supported tuner covers roughly 24–1766 MHz with a suitable antenna. The 2.4 GHz Wi-Fi/Bluetooth bands are outside that range. HF below about 24 MHz needs other appropriate hardware and a supported workflow. Presets are convenient tuning ranges, not permission to monitor a service. Save a station only after checking its frequency and mode. The app does not decrypt encrypted communications.
Read spectrum and waterfall views
The spectrum shows relative received energy around the tuned center. The waterfall shows how that energy changes over time. Confirm the displayed tuning context before comparing captures. A peak can come from a signal, interference, receiver artifacts or overload. Relative levels depend on the antenna, gain, cable, receiver and environment; they are not calibrated field-strength measurements. A quiet plot cannot establish that an area is free of transmitters. Check a known reference and record your receiver setup and coverage limits alongside observations. BandSight does not determine a person’s identity, ownership, intent or legal authorization from a spectrum. Use additional authorized evidence before making decisions about a signal.
Scan supported frequency ranges
Choose Scan, select a supported preset or a permitted custom range, and check its start and end frequencies. Read any displayed band advisory before starting. Start the scan with a connected receiver. Pause or cancel using the scan controls. Retuning and sampling cover a range over time; a short or intermittent transmission can be missed. Inspect a hit before saving it as a station or tuning to it. A stored frequency is an observation and does not prove the device or service behind it. Keep the same antenna and comparable conditions when repeating a survey. No hits with an unverified receiver is an inconclusive result. The website has separate session, expected-emitter and baseline-report tools.
Use the signal finder
Enable the signal finder for an authorized signal you are already tuned to. Watch the relative readout while keeping receiver settings stable. The optional beep provides audible feedback. Reset the retained peak when starting a new comparison so an earlier stronger observation does not confuse the current session. Reflections, obstacles, antenna orientation and gain changes affect apparent strength. A stronger reading is not a distance measurement or proof of a device’s exact position. Stop the finder when done and use it only where you are permitted to work. It does not transmit a locating signal or provide a general Bluetooth/Wi-Fi tracking service.
Capture supported ISM pulse patterns
Choose ISM decode, tune a supported frequency and press Capture. For a device you own or may test, trigger a normal permitted action and observe the received burst. The decoder measures on/off pulse timing and attempts binary/hex representations of supported OOK/ASK patterns. FSK or an unsupported encoding may show energy without producing clean decoded bits. Save selected captures manually, or deliberately enable Auto-save to retain each capture. Review that choice before collecting sensitive identifiers or long sessions. A pattern or fingerprint is not a recovered encryption key or proof that a command can be reused. BandSight never transmits, replays, actuates a lock or advances rolling codes.
Device and button libraries
In ISM decode, create a local device label, add a button label and use Learn for an authorized device. Press that device’s button normally and stop learning when finished. The library groups captured patterns and compares stable portions across observations. Your label is user-entered context, not independent proof of manufacturer, owner or identity. Deleting a device, button or stored codes opens a confirmation. Cancel keeps the existing collection. Clearing codes and deleting a device have different scopes; read the dialog before confirming. Station/signal CSV export is not a complete device-and-button library backup. Keep necessary recovery records separately and check what an exported file actually contains before clearing app data.
Save stations and signals
Save a tuned station or a reviewed scan hit to the station list. In ISM mode, save a selected capture to Saved signals unless Auto-save is deliberately enabled. Search the current collection and use its favorites filter to narrow the list. Stations and captured signals are different collections; the visible list follows the selected operation. Retune from a saved row only after confirming the frequency, mode and authorization. Saving a row does not verify present-day reception or prove that a transmitter is still active. Saved collections remain on this installation. CSV import merges supported station/signal data with duplicate handling. There is no account or cloud synchronization.
Record and export received audio
Start compatible FM/AM reception, then choose Record audio. Recording is optional and captures demodulated receiver audio. BandSight does not request microphone access. Use Stop recording and wait for the completion message. Native recordings are bounded to ten minutes. Interrupted or failed storage must be checked before treating a file as complete. Export recording saves the latest completed WAV through Android’s document picker. Choose a trusted destination and wait for success. A failed or canceled export keeps the private original. The WAV is unencrypted and may contain sensitive received content. Export important completed recordings before starting another session or clearing app data; the visible export action is not a recording-library backup.
Export, import and move your files
Native Export CSV writes supported station or signal rows. Import CSV reads compatible data with validation and duplicate handling. The native reader limits input to 2 MiB and 10,000 rows, with bounded fields; arbitrary spreadsheets and PWA JSON are not native CSV imports. Use Android’s document picker to choose a local folder or an installed provider. If you select Google Drive or another cloud provider, that separate provider handles the upload. The BandSight process has no internet permission. CSV and WAV files are unencrypted. The website’s JSON/CSV exports and downloaded audio are also unencrypted. Choose who may access the destination and apply external file protection if needed. Verify the file opens and includes the intended records before deleting originals. Native station/signal CSV, a WAV recording and a PWA survey JSON have different contents; none should be assumed to restore every feature on the other platform.
Delete data and recover from storage errors
Native saved-row and device/button deletion requires confirmation. Cancel keeps the existing data. Read the specific action before deleting a whole device or clearing its captured codes. If a collection cannot be read, the app preserves the original and protects it from replacement. Do not clear storage just to dismiss that error. Keep recovery copies and contact support with a redacted description. Android backup is disabled. Clearing app storage or uninstalling removes app-owned data and private recordings. AutoSecureLogin has no cloud copy to restore for you. Browser storage is separate: clear the BandSight site’s data to remove its reports, settings and offline cache. Exports already saved elsewhere remain there and must be deleted separately.
Website capabilities and field reports
The website/PWA checks exposed browser capabilities and offers permission-driven Bluetooth selection, NFC or approximate location where supported. It cannot silently enumerate every nearby device or turn a phone into a laboratory spectrum analyzer. WebUSB reception requires a supported browser, compatible receiver and explicit permission. Android native uses USB Host directly. Browser compatibility checks are not proof that a physical receiver works. The PWA stores report observations, survey sessions, expected emitters and baseline comparisons in browser storage. Save an audit or observation to the report, label the session and export its JSON/CSV when needed. Import only a compatible report. Imported values are validated and merged with duplicate handling. A native CSV is not a PWA JSON report, and a browser session does not synchronize with the native station or device libraries.
Receiver proof and baseline comparisons
Before interpreting a quiet result, confirm that the receiver hears a known permitted reference signal with the current antenna and setup. The native receiver provides tuning and spectrum observations; do not assume it has every PWA report control. The PWA’s instrument-proof tool checks reference energy against a median noise floor and records proven, failed or unproven status. A failed or missing proof must remain visible beside survey findings. PWA expected-emitter and baseline tools compare frequency-bearing observations within tolerance. A capability audit or Bluetooth chooser result has no measured RF frequency and is not an unexpected radio emitter. A baseline difference may reflect receiver conditions, changed coverage or a real signal change. Record these limits. Historical receiver tests do not certify your current hardware or prove every frequency was observed.
Band references and reception limits
Use the website band-plan search or native presets to understand the approximate service ranges supported by the receiver. Search frequency values using the selected language’s decimal convention. Allocations overlap, and a caution may come from a broader overlapping service. Read the named caution and region rather than relying on the narrowest displayed band label alone. Band names and open/broadcast labels are reference information, not legal advice or an authorization for your location. Check current local rules and the service operator’s restrictions before receiving, recording or sharing. Encrypted services remain encrypted; BandSight does not recover keys. Unsupported modulation, antenna coverage and receiver frequency limits still apply even when a reference page lists a service.
Offline use and installation
The native application and its bundled help work without Wi-Fi or mobile data. Reception still needs the compatible physical receiver, antenna, power and USB permission. Open the website online and allow its offline cache to finish installing before relying on it away from a connection. A new browser, cleared site data, private mode or storage eviction may leave no cached copy. An installed PWA remains a browser application. Installation does not grant native USB, NFC, Bluetooth or location capabilities that the browser lacks. External support, hardware listings and cloud destinations are separate services. Opening or using them may require internet access in that browser or provider, even though the BandSight Android process stays offline.
Language, larger text and help navigation
Choose EN or ES in BandSight. The native app saves that choice and opens help in the same language. The website stores its language preference separately in the browser. Search help with words from the selected language. Article bodies are included, so a term does not have to appear in the title. Clear the search to restore all topics. All help topics returns to your search; Back returns to BandSight. Rotating help preserves the selected article and query. Use Android’s text-size controls or browser zoom for larger text. Receiver state and a stored collection are different: saved rows persist locally, but an interrupted operation or detached USB device needs a new connection. Check the status when returning from help.
Privacy policy
Effective September 6, 2026. AutoSecureLogin provides BandSight’s native Android app and documentation/PWA. Contact privacy@autosecurelogin.com for privacy questions or requests and support@autosecurelogin.com for product help. This policy describes these products; third-party services have their own policies. Native Android: the app has no internet permission, ASL account, advertising or analytics service. It processes USB receiver identifiers, received samples, settings, station records, signal captures and device/button libraries on the device. USB access requires the system’s user-approved permission. Optional WAV recording contains demodulated received audio, not microphone audio. The native app does not request location, microphone or Bluetooth permissions. Local storage: saved collections and private recordings remain in this app’s Android storage. They are not uploaded to AutoSecureLogin. The app does not claim its local collections or exported files are separately encrypted. Device-level protection depends on Android and the device configuration. Automatic Android backup and device transfer are disabled; keep your own recovery copies. Exports and recipients: CSV files and WAV recordings are ordinary unencrypted files. Android’s document picker lets you choose a folder or installed storage provider. If you select a cloud destination, that provider handles the transfer under its policy. The BandSight process does not upload the file itself. Received content, device identifiers and notes may be sensitive; choose recipients deliberately. Exported copies remain outside the app until deleted at their destination. Website/PWA: the browser stores survey reports, sessions, expected emitters, baselines and language settings locally. Reports can contain device metadata, notes and optional location rounded to three decimal places after you request location access. Bluetooth selection, NFC, location and WebUSB depend on browser support and your permission. The PWA has no BandSight account or report-upload endpoint. Help search runs locally. Website JSON/CSV exports and downloaded audio are unencrypted. Web hosting and external services: loading the website makes normal HTTPS requests. Hosting may process IP address, requested path, time and user agent for delivery and operation; survey content stays in the browser. The site has no advertising or analytics code. External hardware listings, support sites and other linked products receive ordinary requests when you choose to open them. Google Play handles distribution and any store purchase information under its policy. BandSight does not collect payment-card details. Retention and deletion: use the native deletion controls for saved rows, devices, buttons or codes. Clear app storage or uninstall to remove app-owned collections and private recordings. Clear BandSight site data to remove browser reports, language settings and offline files. Browser data may also be evicted or lost in private mode. These actions do not delete exports stored elsewhere. AutoSecureLogin has no server copy of your field collections to recover or delete on your behalf. Support and requests: contacting us shares your address, message and attachments that you choose to send. Redact private recordings, identifiers and locations. Correspondence and operational records may be retained as needed to respond, operate the service and satisfy applicable obligations; no fixed retention period is promised for third-party records. Contact privacy@autosecurelogin.com about information you sent us or rights that apply in your location. Use device/browser controls for records held only locally. Security, intended use and changes: protect the device and exported files and follow reception, recording and sharing rules. No software can guarantee protection on a compromised device. This field tool is intended for authorized users and is not directed to children. Material policy changes will be published with a revised date. AutoSecureLogin does not sell locally handled survey content or use it for advertising.
Terms of use
Effective September 6, 2026. These terms cover AutoSecureLogin’s BandSight native Android app, website, documentation and PWA. Use them only with equipment, signals and locations you are authorized to examine. Product questions go to support@autosecurelogin.com. Receive-only boundary: BandSight receives and analyzes supported signals. It does not transmit, jam, replay radio commands, unlock devices or recover encryption keys. Receive-only design does not itself grant permission to intercept, record, retain or share a communication. Follow applicable law, service restrictions and your organization’s authorization. Scope and compatibility: native reception needs supported USB Host hardware, receiver, tuner, antenna, power and permission. Browser features depend on the browser and device. References and presets are approximate guidance, not a guarantee of coverage or a current legal determination. Unsupported modulation and encrypted communications may not produce intelligible results. Interpretation: spectrum levels are relative observations, not calibrated field-strength readings, guaranteed identities or precise locations. A failed or unperformed receiver check cannot certify a clear area. Baseline differences, fingerprints and decoded patterns require context and independent verification. Do not treat an empty report or historical hardware test as proof of present-day absence or safety. Your records: review what you collect and whom you share it with. Local data and exports may contain sensitive content and identifiers. Exports are unencrypted. Maintain independent recovery copies; automatic Android backup is disabled. Native CSV, WAV and PWA JSON have different scopes and are not interchangeable whole-app backups. AutoSecureLogin cannot restore data it never received. External services and purchases: third-party hardware sellers, browser providers, Google Play, storage destinations and linked products set their own terms. If a store offers a paid download, its displayed price and applicable refund rules apply. The app does not provide hardware, a hosted monitoring service or an ASL subscription. Any separately offered voluntary contribution does not promise a feature unlock, ownership, priority service or charitable tax treatment. Availability, warranty and liability: to the extent allowed by applicable law, the software and references are provided as available without a guarantee of uninterrupted operation, accuracy, recovery or suitability for every deployment. AutoSecureLogin does not control your radio environment or third-party equipment and is not responsible for unauthorized use. Nothing excludes rights or liabilities that cannot lawfully be excluded. Privacy, support and updates: the accompanying privacy policy explains local data, browser permissions, exports and support communications. Contact privacy@autosecurelogin.com for privacy requests. Support is not an emergency or guaranteed managed-survey service. Updated terms will have a revised date. When finished, stop receiving and recording; remove local data and external copies separately as appropriate.