IMPROVE BATTERY LIFE OF A MOBILE FLEET
summary
Greenspector uses the Power Test Cloud device farm and UI tests driven by UI Automator plus a start/stop measurement API to profile five candidate phones (Bluebird, Zebra, Copernic, Famoko, Samsung) and project usage across a fleet of 16,000 devices. Tests find a Bluebird idle CPU bug, 2G dramatically shortens runtime so many configs fail the 8 hours autonomy target, AirWatch halves battery life versus no MDM, and Cordova raises memory and energy compared with native (Crosswalk trades energy for more RAM).
AI-written summary · about
chapters (11)
- 0:00Introduction and context
- 1:50Stakes of eco-design
- 5:26SNCF Cosmo project overview
- 9:01Test automation and methodology
- 11:05Device selection challenges
- 12:30Choosing the best device
- 14:37MDM impact on battery life
- 16:02Framework selection trade-offs
- 18:12Optimizing idle phases
- 19:14Network control strategies
- 20:16Key recommendations summary
related talks
38mTowards Zero Carbon: Implementing Sustainable Battery Lifecycle...
57mOff to a good start
46mMobile & IoT Integration Testing
27mLow power design: where are we at?
36mUsing sensors to reduce wasted support time: case study for testing in IoT
10mLightning Talk: From Ideas to 3 Firmwares Powering Railway-Infrastructure Monitoring...
29mLow Power Mode, iBeacons and MFi
17mMinimizing CO2 Impact from Concept to Deployment in Smart Buildings