Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polar H10 Internal Recording doesn't work for long measurement - 24 hrs #396

Open
3 of 10 tasks
carldatu opened this issue Sep 13, 2023 · 5 comments
Open
3 of 10 tasks
Labels
bug Something isn't working

Comments

@carldatu
Copy link

carldatu commented Sep 13, 2023

Platform on which you observed the bug:

  • Android
  • iOS
  • Other
  • Platform is not relevant for this bug

Device on which you observed the bug:

  • Polar OH1
  • Polar Verity Sense
  • Polar H10
  • Polar H9
  • Other
  • Device is not relevant for this bug

Describe the bug
I tried to start internal recording with Polar H10 device for 24 hrs. After finish the training, I could not get the recording sample data from Polar H10 device.

How to Reproduce
Start internal recording for long time (ex. 24 hrs). Finish recording.
When try to get recording data from that exercise, app doesn't work.

Expected behavior
Polar H10 Manual says max internal recording duration is 30 hrs. so for 24 hrs internal recording, it should work properly.

Screenshots and logs
Here is log when get the recording data from 24 hrs measurement.
So basically, To get recording sample data, app call the fetchExercise api for Android and it raise the below error.
com.polar.androidcommunications.api.ble.model.gatt.client.psftp.BlePsFtpUtils$PftpOperationTimeout: Air packet was not received in required timeline

Here is logs

2023-09-13 15:53:33.447 9412-9412 ViewRootIm...nActivity] com.polar.androidblesdk I ViewPostIme pointer 0
2023-09-13 15:53:33.677 9412-9412 ViewRootIm...nActivity] com.polar.androidblesdk I ViewPostIme pointer 1
2023-09-13 15:53:34.193 1736-1736 LayerHistory surfaceflinger I com.polar.androidblesdk/com.polar.androidblesdk.MainActivity$_9412#17648 Max (can't resolve refresh rate)
2023-09-13 15:53:55.302 2494-4542 SGM:GameManager system_server D identifyForegroundApp. com.polar.androidblesdk, mCurrentUserId: 0, callerUserId: 0
2023-09-13 15:53:55.302 2494-4542 SGM:PkgDataHelper system_server D getGamePkgData(). com.polar.androidblesdk
2023-09-13 15:53:55.967 9412-9741 BluetoothGatt com.polar.androidblesdk D onClientConnectionState() - status=0 clientIf=6 device=C943FC_2
2023-09-13 15:53:55.978 9412-9625 BluetoothGatt com.polar.androidblesdk D setCharacteristicNotification() - uuid: 00002a37-0000-1000-8000-00805f9b34fb enable: false
2023-09-13 15:53:55.986 9412-9625 BluetoothGatt com.polar.androidblesdk D close()
2023-09-13 15:53:55.993 9412-9412 MainActivity com.polar.androidblesdk E Failed to read exercise. Reason: java.lang.Exception: com.polar.androidcommunications.api.ble.model.gatt.client.psftp.BlePsFtpUtils$PftpOperationTimeout: Air packet was not received in required timeline
2023-09-13 15:53:55.996 9412-9625 BluetoothGatt com.polar.androidblesdk D unregisterApp() - mClientIf=6

@carldatu carldatu added the bug Something isn't working label Sep 13, 2023
@samulimaa
Copy link
Contributor

Hello,

Thanks for reporting this, I have created an internal ticket for further investigation.

Best regards,
Samuli

@carldatu
Copy link
Author

Thanks, I hope to fix it ASAP.

@infomus
Copy link

infomus commented Feb 26, 2024

We're experiencing the same issue on Android A8 Tab when calling startRecording. Is there any update on this yet?

@orestesgaolin
Copy link
Contributor

Wondering if there's any update on Air packet was not received in required timeline issues?

@smyffanon
Copy link

smyffanon commented May 11, 2024

Wondering if there's any update on Air packet was not received in required timeline issues?
for me the frequency of the issue went way down when my Moto g8 power broke and I went to a google 6a.

It's was happening now once every 3 to six months instead of 2x per month.

and a after I experienced that reduction for maybe 8 months I got some time and installed a new version of the API that the staff here said would reduce the frequency of the issue, and I think it reduced a bit more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants