No ecg file

[NeilP1966]

Hello Ian, I carried out a resting session yesterday with artifact sensitivity set at 5% and some artifacts did show over the course of 6 minutes however I do not see a .ecg file in the list. Also, when I ran the app this morning it stopped working after 1 min 50 seconds. Do you want to see the debug file?

[IanPeake]

Hi, thanks for the report. Yes, please do share the debug file. Privately if you prefer at the email address in the README.md.

[IanPeake]

Are you able to share your current version of the app, using the App Info from the running app?

[NeilP1966]

Hello Ian, really sorry about the lack of response from me on this. I used the email address in the readme but it seemed to end up with a completely different person somehow. Anyway, I'll continue to use the app and let you know if I encounter any further issues.

[mikedanielak]

I'm having this same issue. I'm using the public release version in the Play store running on a Pixel 4 running Android 12 and a Polar H10.

ftmxr_20220103093642.debug[1].log

[IanPeake]

Thanks. Can I just check that you have developer mode enabled?

On Tue, 4 Jan. 2022, 1:54 am mikedanielak, @.***> wrote:

I'm having this same issue. I'm using the public release version in the Play store running on a Pixel 4 running Android 12 and a Polar H10.

ftmxr_20220103093642.debug[1].log https://github.com/IanPeake/FatMaxxer/files/7802523/ftmxr_20220103_093642_.debug.1.log

— Reply to this email directly, view it on GitHub https://github.com/IanPeake/FatMaxxer/issues/28#issuecomment-1004146250, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFSEU6JTGAJLF4U7I4ZLSKLUUG2DDANCNFSM5AMD75VA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

[NeilP1966]

I'm having this same issue. I'm using the public release version in the Play store running on a Pixel 4 running Android 12 and a Polar H10.

ftmxr_20220103093642.debug[1].log

I also don't see any ecg files, I've been using developer mode since first app installation, using an Android phone v11 and a Polar H9.

[mikedanielak]

I have developer mode enabled. I've since intermittently gotten an ecg file.

I was asking Bruce Rogers about how my DFAa1 could be so low when I have actual lactate measurements. He thought maybe one issue was the orientation of the H10 and wanted me to send an ecg file which I wasn't able to do. He suggested I sideload a later version of the app, or use the polar sensor logger app (which I've been using for months for my workouts).

I can't sideload apps because I use my phone for both personal and work use and work makes me install a mobile device management program that won't let me side load apps for security reasons.

The polar sensor logger app wouldn't create or graph an ecg file either. It's Google Play page says it needs firmware version 3.0.35 or later. I noticed that I was on 2.1.9, but the Polar Beats app wasn't offering an update. After scrounging around on the internet, I found others with the same issue and apparently you have to also download and install the Polar Flow app and create an account and then the Flow app actually offers the update. I did all this and it offered two updates in a row and now I'm at version 3.1.1.

I immediately started fatmaxxer and saw it created an ecg file. I did this 2 or 3 times and saw 2 or 3 sets of logs including an ecg and figured my problem was solved. I went down on my bike to do a quick workout under load and capture an ecg file for Bruce. Unfortunately, it didn't create one for that workout (and it was still in developer mode). I was able to create an ecg file in the polar logger sensor app, or at least appear to. It will run for a bit and will say "waiting for ecg" and then after it started to display a number (some number of microvolts), it would run for 5 seconds more and hang up.

I tried fatmaxxer again and got an ecg file so it's intermittent now. I haven't opened and actually tried to graph the file yet.

[IanPeake]

@mikedanielak Thanks for the excellent troubleshooting. I will add some corresponding advice to the FatMaxxer FAQ.

It does look like there is a residual issue regarding saving of ECG logs. In dev mode there should always be at least one ECG trace triggered automatically at around the 10s mark. Relatedly, may I ask whether the debug.log file you shared is readable by you? I see garbage when I load this in a text editor, as though my editor is using an incorrect character encoding.

[IanPeake]

@NeilP1966 I'd be interested to know whether @mikedanielak 's advice to upgrade the H10 firmware helps you at all?

[IanPeake]

For reference, the H10 I'm currently using is at firmware version 3.1.1. I believe this is a new unit which probably shipped with that version.

[mikedanielak]

I can read the debug load I posted. This was before the firmware upgrade. Since I was trying to create an ecg file, I searched for "ecg" in the log and saw this:

startECG create ecgDisposable ECG throwable class polar.com.sdk.api.errors.PolarServiceNotAvailable

[NeilP1966]

Hi Ian, I've just followed the advice ref Polar Flow and will check my strap firmware when I do my session tomorrow and will let you know.

[IanPeake]

@mikedanielak - thanks again, I can read your log file. If/when you see this issue again, it would be great if you could share the new debug.log

[IanPeake]

@NeilP1966 - thanks. As for Mike, if you could share a new log file with this issue and the new Polar firmware that would be great.

[NeilP1966]

ftmxr_20220103093642.debug.1.log

@IanPeake hopefully this works

[IanPeake]

Thanks @NeilP1966 , what firmware version is your H10 on? (I need to check whether the Polar API will report this so it can be included in the FatMaxxer log.)

[NeilP1966]

@IanPeake I actually use a H9 not a H10

[IanPeake]

@NeilP1966 Sure. What firmware version?

[NeilP1966]

1.0.6

[NeilP1966]

@IanPeake From what I can find it seems my H9 and both apps are up to date.

[IanPeake]

@NeilP1966 Something's amiss. The debug.log file you linked to seems to have the same name and contents as the one @mikedanielak provided. Moreover it reports seeing a Polar H10: "BDDeviceList/new session added: Polar H10 2F0F032D". Can you double check your sensor DEVICE_ID and try re-uploading the log file?

[NeilP1966]

@IanPeake How odd, that came straight off my phone. I'll have another look when I get to work.

[NeilP1966]

ftmxr_20220104160301.debug.log

@IanPeake Hello , here is a file from a 60 min easy session I did this afternoon.

[IanPeake]

@NeilP1966, I suggest trying to get an ECG sample using another app, for example Polar Sensor Logger (https://play.google.com/store/apps/details?id=com.j_ware.polarsensorlogger). Sorry for the bad news but it appears that the H9 does not in fact support ECG sampling although it is difficult to establish this from the Polar official specs. The debug.log file you provided shows the error polar.com.sdk.api.errors.PolarServiceNotAvailable; I'm still searching for Polar SDK documentation to clarify this. The Polar SDK docs for the H9 (https://github.com/polarofficial/polar-ble-sdk#h9-heart-rate-sensor) do not mention ECG sampling. The Polar Sensor Logger app linked above also does not mention ECG samplling for the H9.

[NeilP1966]

@IanPeake Hello Ian, I was using your app yesterday and towards the end of my ride my artifacts were seriously racking up. Today, using HRV Logger I saw the same thing. I now believe this was due to my H9 breaking in some way as it now pairs to both apps bit will not provide readings. So, I've got a H10 on order and will see what that produces when i do a session with it.

[NeilP1966]

@IanPeake Hi Ian, all good ref the H10, I've sent some files to Bruce and he has advised on the best body position for me to get the best voltage signals. One question though, what happens for the first 2 minutes of a recording? I was looking at the timestamps in a csv yesterday and the first line was at 125 seconds. I like to add a column which lines up my power readings with the alpha1 readings so it wouid be nice to know how to coordinate the start of a session with the start of Fatmaxxer data samples. Thank you.

[MedTechCD]

There is no recording of a1 during the first 2 minutes because you need a 2 minute window with steady state to calculate a valid dfa-a1. First value appears in the features file after 2min.

[NeilP1966]

@IanPeake that's what I concluded, thanks