Most of the builtin apps had some padding between the window edge and
their content, because they expect to be displayed with a line border on
their edge. We added a customization option to remove the border, so,
that padding is not always necessary. Make the layouts dynamically
adjust, to omit the padding when it isn't needed.
Handle left/right swipes on the tab bar, not just up/down
Update All button on the Updates page main list
Scroll by pages rather than lines on the permissions list
The previous commit's comment and test said Android starts the app in the
background (a home-widget update, a notification-listener rebind) with
the glasses session running. A background start alone doesn't connect
the glasses; only the main page does. The state that breaks voice is
the Activity being destroyed afterwards: swiping the app away in Recents
destroys it while the foreground service keeps the process and session
running, and NativeScript then clears both foregroundActivity and
startActivity. On Android 12+ Back on the main page only moves the task
to the back, so the Activity survives it. Comment and test wording only.
ensurePermissions looked up the Activity before checking whether any
permission was missing, and getActivity() throws when there is none.
Android starts the app in the background with no Activity (a home-widget
update, a notification-listener rebind), and the glasses session runs
from there until the app is opened. So in that state every "Hey Even"
failed in ensureVoicePermissions even though the mic permission was
granted, and the voice dialog kept showing the idle "Voice control
stopped.". The same throw hit ensureBlePermissions.
The Activity is now only looked up when a permission actually has to be
requested. A capture that fails to start for any reason other than a
denied permission now says so in the dialog instead of leaving the idle
status up.
Only the settings reply says the glasses are charging. Outside charging
mode it is polled every five minutes, and not at all while the display
is suspended, which it is once the glasses come off the face. So after
docking, the phone kept showing the glasses as "Not charging", and
charging mode (which pauses display traffic) didn't start until the
display woke or the link reconnected.
The case push that reports the glasses going from out of the case to
docked arrives within a second. It now schedules a battery read about
three seconds later. The drive loop queues it as a pending message,
which still goes out while the display is suspended.