COMING SOON · Q1 2027 Planned releaseGet notified + 10% launch offer ↗
← Acorn overview

Acorn application guide

Android Collector

The Android collection interface presents an authorised logical-acquisition route. Device state, authorisation and operating-system version determine what can actually be collected.

Collection controls shown

What authorised logical collection route is suitable for this Android device?

Start with

  • The reference ADB collection interface and device-authorisation requirements; no handset was connected for this screenshot.

What you can take away

  • Device-listing and logical-collection controls; no completed extraction is shown.
The native Android Collector presents authorised ADB logical collection, device listing and optional legacy backup controls. View full screen
The native Android Collector presents authorised ADB logical collection, device listing and optional legacy backup controls.

Open the screenshot and choose “View actual size” to read the records at their original resolution.

A practical starting point

How the workflow fits together.

  1. Confirm authority and the intended collection scope.

  2. Check device authorisation and version-dependent collection options.

  3. Validate the available route on a suitable test device before agreeing expected coverage.

Start with your requirements

Bring a sample question.

Ask us to demonstrate this workflow with suitable public or constructed material. Do not send confidential evidence in an initial enquiry.

Planned for Q1 2027

Be first to hear. Save 10% at launch.

Request Acorn launch news and details of the planned 10% offer. No deposit or purchase commitment.

Notify me at launch ↗

Launch-update requests go to the SQFR team for review. Final offer terms and product availability are still to be confirmed.

About the screenshots and illustrations

Application screens are selected from the September 2026 Acorn screenshot pack. Captions distinguish native setup views, constructed training records and public-corpus results. They are not private client cases, and a displayed control does not establish that every operation was completed.

Relevant public sources include DeepBlueCLI training event logs and Plaso test data. Check the relevant source terms before redistributing an underlying dataset.

Workspace scenes and sector mascot variants are generated illustrations. They do not show actual police, judicial, military or university deployments or endorsements. The original Squirrel Forensics identity is retained.

Zoom in, then scroll to inspect the detail.

Open full-resolution image ↗

A useful first conversation

Let’s look at your workflow.

Tell us what you examine, where you work and what you need to deliver.

Use the enquiry form to outline your role, intended use and potential order quantity. Do not send case material through a general enquiry.

Your enquiry goes to the SQFR team. Please do not include passwords or case evidence.