Keep awake

It is never a bare activate: a screen that holds the display on and never releases it is a phone that never sleeps, which the user experiences as a battery fault and never attributes to the app that caused it. hold() always returns the function that releases it.

Install

npx expo install expo-keep-awake

import { KeepAwake } from '@ng-native/expo/keep-awake';

The smallest useful example

import { Component, DestroyRef, inject } from '@angular/core';
import { KeepAwake } from '@ng-native/expo/keep-awake';

@Component({
  selector: 'app-recording',
  template: `<text>Recording...</text>`,
})
export class Recording {
  constructor() {
    inject(DestroyRef).onDestroy(inject(KeepAwake).hold('recording'));
  }
}

What it does

• hold(tag) - holds the screen on under that tag, and returns the function that releases it. The tag defaults to a package-wide constant, but naming it explicitly is what lets two screens each hold the screen on without either releasing the other's hold.
• holders - a signal of the set of tags currently holding the screen on, for a debug screen that wants to say which.
• active - whether anything currently holds the screen on, computed from whether holders is non-empty.

Releasing the same hold twice does nothing the second time.

Without the module installed

hold() still tracks the tag in holders and active, but nothing on the device changes and stop calls into a module that is not there safely.

Reference