Ive recently started development for Tizen OS. My app was created for socks only and only for a specific device, which is Samsung Gear Sport (Tizen 3.0 on board). The main purpose of this application is to collect complete sensor data over a long period of time. I am interested in heart rate and motion sensors in general (gyroscope and accelerometer). Then this data will be sent to the cloud server and analyzed. I am currently considering a WEB application because so far I have not found any evidence that the web API is missing what exists in the native API.
But there is one limitation in Tizen OS that I still cannot overcome. My application falls asleep after a while (10 minutes or so). It is imperative that this application runs in the background for a long time (up to 10 hours). To achieve this, Ive tried the following approaches:
- A typical Tizen app with a reference category: the data given by this approach is still too fragmented, for example, I got 15-minute holes where no data was recorded at all. Sometimes there were holes even longer than 30 minutes.
- Tizen API alarms: performed this work when the application was saved, but with each alarm the application was brought to the forefront, and this is not an acceptable solution. It is possible to wake the application silently (using the management application), but it does not have a callback, so all alarms must be scheduled in advance.
- the CPU_AWAKE flag caused the system to display a pop-up window saying “this application is using too much power”, and when no response is received within 10 minutes or so, the system will kill my application anyway.
- Web site workers are just for the sake of argument, web workers go to bed with the application
- : - Apple Health Kit, -, HRM. -
PRESSURE. Tizen HRM, - NotFoundError: Failed to read recorded data. TypeMismatchError. - - - Samsung, , .
- "keep always on", true . Ive. Watch face , , . , , .
: , . , , , , 10 , . , , , , .
: 10 ?