galaxy | HTML5 Canvas Galaxy - Demo : https : //kurisubrooks | Canvas library

TL;DR how can I have an Android sensor permanently running/active/registered for my app, even if I close it?

Objective:
I'm making a Flutter application that counts your steps using the pedometer package,
which uses the built-in sensor TYPE_STEP_COUNTER of Android,
which returns the # of steps taken since last boot (iOS). On Android, any steps taken before installing the app are not counted.

How I implemented it:

• When the app is actively running in the foreground, each step causes a myStepCount to increment by 1.
• In all other cases (phone locked, went to home-screen, closed the app...), the android TYPE_STEP_COUNTER sensor should still be running in the background, and once I open my app again, the difference between new stepCount and last saved stepCount (saved using shared_prefs) will be calculated and added to myStepCount.

Important:
The TYPE_STEP_COUNTER sensor must be permanently running/stay registered in the background, even after I lock my phone, go to the home-screen, or close the app...

Observations:

• On my Samsung Galaxy A02s, my app works perfectly fine, as it it supposed to (as described above). That is because on that phone I also have the Google Fit app installed, which tracks your steps 24/7 (so the TYPE_STEP_COUNTER sensor is permanently registered).
• On my Samsung Galaxy S7, my app does not work as it's supposed to. myStepCount gets incremented when I take steps while the app is running in the foreground. But steps taken while the app is closed will NOT be added to myStepCount once I open the app again.
  Note: I don't have any other step-counting-apps like Google Fit on this phone.

Conclusion:
I need to find a way to register the TYPE_STEP_COUNTER sensor from my Flutter app, and keep it registered even after I close the app.

2 Attempted (but unsuccessful) Solutions:

1st Attempt:
Calling Native Android Code from my Flutter Code to register the sensor
This is my main.dart file (with the unimportant parts left out for simplicity):

I have implemented biometric authentication in my application with biometric level BIOMETRIC_STRONG (Class 3). The fingerprint authentication is working as expected but I couldn't able to test the face authentication on any of my devices (Samsung Galaxy S10, Oppo A3S, etc.). I think the face authentication in those devices is not falling under Class 3.

Are there any Android devices with BIOMETRIC_STRONG (Class 3) face authentication? It would be helpful if someone can provide a list.

They know how to implement the scroll by bezel (Galaxy watch 4 Classic) in wear os 3.0 with jetpack compose

In the documentation it mentions the use of ScalingLazyListState or ScrollState but so far the scroll with the rotating bezel of my device has not been recognized.

if anyone has information or an example it would help me a lot.

I've been trying to write a simple vibration app for my Samsung Galaxy 4 watch but am having an issue. The watch will not vibrate when the screen is off. It will only vibrate when my application is open. Any ideas why this is? Here is some of my code:

My app requires precise user location because it requires the user to be at specific locations to perform tasks. I have followed the documentation for the proper way to request both ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION together.

I was having a hard time figuring out how to phrase this. Sorry if this is a noob question, I'm new to responsive design and mobile web design in general.

My phone (Galaxy s10e) will render my webpage as if it's 360 pixels wide, with all elements positioned appropriately based on this width. I have several image tags on the site that are the same width. I was using src images that are 360px wide, and this looks fine on desktop because it is actually rendering my images at 360px, but on mobile the images alone appear to be rendering at a much higher resolution, causing it to look terrible due to upscaling.

If someone could explain to me what is happening here it would really help, since I can't find information on this specific behavior. Some questions I have:

• Is the browser choosing to position the elements based on a 360px width while rendering the actual content at the screen's resolution?
• How do I account for this in my design? I considered rendering the images at the higher resolution and then having the page dynamically scale those images down (so even though the actual div is 360px, the browser can use the 'extra space' allotted by max-width to render the image at a higher resolution), but I want the images to remain 360px wide on desktop, not the higher max-width for mobile rendering.
• Where can I learn all about this behavior so I know how to tackle responsive image scaling in the future?

Thank you for your time. Let me know if you have any other questions. I'm using ReactJS to develop the site.

I want to let the user switch the whole document between LTR and RTL. Some CSS properties have start and end values that follow the direction of the document. Most geometrical relations are though absolute.
I want to do something like this if possible, in plain CSS without Javascript and without reloading the document:

if dir is ltr
use padding-left: 65px;
if dir is rtl
use padding-right: 65px;

Edit: Here is i complete list of logical properties and values, so adding a conditional properties may not be needed altogether. Note though that some or all will not work on few years old browsers. My 4yo Galaxy s8 for instance, has never updated its native browser who did not support logical.

Edit2: See now that float: inline-start and inline-end are only supported by Firefox, so back to conditional CSS,

I tried to cluster my dataset using K-mean, but there is a categorical data in column 9; so when I ran k-mean it had an error like this:

So I have multi-class classification. I want to compile my model: