• State Verified Answer
  • Replies 13 replies
  • Subscribers 20 subscribers
  • Views 630 views
  • Users 0 members are here
Options
Related

This setting will reduce battery life

Valeriy Kovalenko
6 days ago

Some users of my app have started seeing this screen when they launch the app (sorry for the quality — this screenshot was sent by a user):

They get stuck on this screen.
My question: where can I find any documentation about it? I can’t reproduce it in the simulator or on my own device (Descent MK2). I don’t really understand how to fix it.

Since this appears to be a system screen, I would expect the green button to return the user to the app — but it seems like I may need to handle that manually somehow.

Kind regards,

Valeriy

  • 0 5 days ago

    I can see such screen from time to time when battery is low. Rather not connected with any app, system future.

  • 0 5 days ago

    Ask the user to send a video. I think this is not caused by changing a setting in your app but some system setting.

  • 0 5 days ago

    This must be something related to the app. Many users see this screen right after starting the app and cannot get past it. Here’s another photo I received this morning from a different user:

    If you have a device with an AMOLED screen (all the reports I received came from users with AMOLED-screen devices), you can give it a try:

    apps.garmin.cn/.../052e2b7b-e72c-46f8-bcb6-8b941e35d9fb

  • 0 5 days ago

    Hilariously enough I saw this prompt on my FR955 just as I was reading this post (I was in the Settings > Health & Wellness menu after I dismissed it), but I don't know how to recreate it. (I did try toggling a few of settings in that menu, and in the Wrist HR submenu).

    (In my case it didn't seem to have anything to do with a CIQ app.)

  • 0 5 days ago in reply to Valeriy Kovalenko

    Can you share the permissions section of the manifest and the code that enables sensors? Maybe there's some combination that triggers this?

  • 0 5 days ago in reply to FlowState

    I'm able to trigger the prompt at will now, by changing Settings > Health & Wellness > Pulse Oximeter to All Day

    (idk if it's how I originally triggered it)

  • +1 5 days ago in reply to FlowState

    I'm also able to trigger the prompt within a CIQ device app as follows:

    - Created a new project with type "watch app"

    - Added the following line to my app class's initialize() function:

    Sensor.setEnabledSensors([Sensor.SENSOR_ONBOARD_PULSE_OXIMETRY]);

    - Enabled the Sensor permission

    - Sideloaded to fr955

    When the app is launched, the prompt is displayed. I can answer yes or no to the prompt, and regardless of my answer, the app proceeds as normal (other than the fact that the pulse ox sensor probably wasn't enabled if I answered no).

    idk if things are different in other devices, or if setEnabledSensors is being called in your (OP's) app in a different place where the prompt is somehow unanswerable. Either way I would call that a bug:

    - the wording of the prompt is bad in the context of a CIQ app which turns on the pulse ox sensor without necessarily requiring an explicit action from the user [so the user and dev have no idea what it means]

    - if the prompt is unanswerable under any cirumstances, that's a serious bug

    It's just another case of a generic device change impacting CIQ in an unforeseen way (because nobody bothered to think of CIQ when the change was made).

  • 0 5 days ago in reply to FlowState

    Thanks! This is what’s causing the issue. My app reads SpO2, and when the user changed this setting to “All Day,” they were able to start the app without any errors.

    I still think this is a system-level issue that should be handled properly (so the app doesn’t get stuck on a screen with non-working buttons), but at least now I know a workaround.

  • 0 5 days ago in reply to Valeriy Kovalenko

    Yeah I would post a bug report for the 2 problems:

    - obscure / meaningless prompt (outside of the context of the system pulse ox setting)

    - impossible to answer prompt in some mysterious cases

  • 0 5 days ago in reply to FlowState

    I also find it super weird that OnboardSensorType includes both SENSOR_PULSE_OXIMETRY  and SENSOR_ONBOARD_PULSE_OXIMETRY, but only the latter sensor type triggers the prompt?

    What exactly is SENSOR_PULSE_OXIMETRY for?