Egocentric Electronics and Device Repair Video Data

Egocentric electronics and device repair video data is real-world, first-person video of a person repairing an electronic device: working out what is wrong, opening the housing, removing and replacing a faulty part, closing the device up and testing it. It is recorded from the operator viewpoint, with depth, 3D hand pose, contact events and frame-accurate action segments aligned on one hardware clock.

Repair differs from assembly in its order of work. An assembler follows a known build sequence; a repairer starts from a fault, takes the device apart in reverse, decides which part has failed and then rebuilds. The electronics assembly page covers placing components, soldering and building devices, and the cable routing page covers wiring. This page covers fault-driven work on devices that already exist.

The site states device repair in its task catalog, in two environments. An Electronics & Device Repair Shop environment lists one Device Repair row. A separate Repair Shop environment, covering appliance, bicycle, shoe, watch and furniture work, lists an Electronics repair row, an Appliance repair row and a Watch repair row alongside bicycle, shoe and furniture rows.

Every row uses the same capture mode, a head-mounted phone or a multiview rig. All four rows are rated Hard, and none is rated Easy or Medium.

The catalog row reads "Diagnosing and repairing phones, laptops, tablets and consumer electronics." The example it gives for the environment is a phone, laptop and consumer electronics repair counter. It is the only row in the Electronics & Device Repair Shop environment, and it is listed as Active collection, which means recording is running now.

The row names categories of device, and no more. Device models, brands and the number of devices per session are Not stated, so they are set in the written spec.

The Electronics repair row reads "Open the device, diagnose the fault, replace the screen, battery or board and test." It is rated Hard and listed as Available on request, so its timeline is quoted against your spec.

The Appliance repair row follows the same shape for appliances: "Open the appliance, test components, replace the faulty part and reassemble." It is rated Hard and Available on request.

The Watch repair row reads "Open the case, replace the battery or movement parts under magnification and reseal." The site does not say whether the watch is electronic, so this page lists it as neighbouring work and does not count it as electronics repair.

It is the only row that mentions magnification, and it mentions it as part of the task. The site does not state a macro lens, a magnified camera view or any close-range capture setting for repair, so none is claimed here.

The catalog lists several electronics rows that build, solder or break down devices instead of repairing them. Circuit board assembly places components, seats connectors and secures parts before soldering. Component soldering solders components to a board with an iron and solder wire, trims leads and inspects joints. Device manufacturing assembles housings, fits boards and cables, fastens screws and tests the unit. E-waste disassembly and sorting unscrews and pries open devices, removes boards and batteries and sorts materials into bins. A through-hole soldering row sits on a separate precision assembly bench.

None of those rows names a fault, a diagnosis or a replacement, so this page keeps them as neighbours.

The catalog places the single Device Repair row in an Electronics & Device Repair Shop environment, with a phone, laptop and consumer electronics repair counter as the example. The other three rows sit in a Repair Shop environment whose examples include electronics repair, appliance workshop and watch repair.

The site names no shop, brand or technician, and does not state capture at a customer own facility. Environment, access and schedule are agreed in the spec.

A head-mounted phone records the first-person view of real work on site, and a multiview rig adds synchronized third-person angles when the spec asks for them. A wrist-mounted camera is available alongside the head camera for close-range detail.

The site does not state a camera count, resolution or frame rate for repair. Tools and soldering equipment, component sizes, magnification or macro capture, and the number of sites or technicians are Not stated, so raise them in the spec.

Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. For repair, hand pose tracks the fingers lifting, easing and seating a part, contact events mark when fingers meet a tool or part, and action segments mark each step.

Object labels use the terms your spec sets. Device types and models, tools, component sizes, throughput, force or tactile data and a repair-outcome or task-completion label are Not stated. They are defined in the spec if your policy needs them, and no electrostatic discharge, battery-safety or certification claim is made.

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd. The format table below sets each against what its official documentation states. Repair episodes use the same schema as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes.

Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch.

Every episode links to a signed contributor release through a documented consent chain, and the consent record is part of the delivery. Faces, plates and screens are detected and irreversibly blurred at ingest, and a reviewer confirms the result before anything ships. The anonymization record is delivered with the data.

That is the whole of the privacy wording the site states. It does not state a rule for customer data stored on a device, a data wipe before repair, or serial numbers and labels on a casing, so this page makes no such claim. Raise it in the spec if it matters.

Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck, and we quote that up front.

On-demand top-ups run against the same spec and accept criteria after each training run. The site does not state a batch size or later-batch turnaround, so those are quoted against your spec.

You describe the devices, faults and sequence your policy needs. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price before any capture begins.

A Spec Pilot, a small and fast first batch, can prove the spec and accept criteria before you scale. Billing is per validated hour, a reject log ships with every batch, rejected items are recaptured at our cost, and every collection ships under a perpetual, buyer-owned commercial license.