Battery life sounds like one number, but it depends on workload, brightness, connectivity, temperature, and test method. Oneira's current specification table marks capacity and runtime as pending production validation. That is a boundary, not an invitation to estimate publicly from a prototype.
Define the workload before the hours
An idle face at low brightness and frequent connected image requests are different tests. A useful runtime claim names display behavior, interaction frequency, network conditions, temperature, and the point at which the test ends. Without that method, two hour figures cannot be compared honestly.
Production hardware can change the result
The final production configuration and software tuning can differ from a prototype setup. Validation should use representative production units and repeatable tests, not an ideal bench sample chosen because it produced the longest number.
Publish a range with context when ready
A responsible result can include a typical scenario, heavier-use scenario, charging assumptions, and factors that reduce runtime. Owners can then plan without treating one maximum as a guarantee. Until those tests exist, the accurate answer is that final battery capacity and runtime remain pending.
The short version
- Runtime is meaningful only when the workload and test method are defined.
- Representative production units should support the published result.
- Pending validation is more honest than a prototype-based promise.