are you keeping qz always on foreground?

Yes, QZ is open and in the foreground the whole time.

got the error @AnneAstrid88 it seems that your phone is missing some beats

Mon Nov 27 06:53:10 2023 1701064390802 Debug: ../src/trainprogram.cpp void trainprogram::scheduler() "trainprogram elapsed 176current row len104"
Mon Nov 27 06:53:12 2023 1701064392998 Debug: ../src/trainprogram.cpp void trainprogram::scheduler() "trainprogram elapsed 177current row len104"
Mon Nov 27 06:53:15 2023 1701064395550 Debug: ../src/trainprogram.cpp void trainprogram::scheduler() "trainprogram elapsed 178current row len104"
Mon Nov 27 06:53:18 2023 1701064398409 Debug: ../src/trainprogram.cpp void trainprogram::scheduler() "trainprogram elapsed 179current row len104"
Mon Nov 27 06:53:21 2023 1701064401511 Debug: ../src/trainprogram.cpp void trainprogram::scheduler() "trainprogram elapsed 180current row len104"
Mon Nov 27 06:53:24 2023 1701064404197 Debug: ../src/trainprogram.cpp void trainprogram::scheduler() "trainprogram elapsed 181current row len104"

we should see these lines every seconds, but instead some seconds are missing. which phone do you have? maybe it's with a power save mode?

Device: Pixel 7 Pro
OS: Android 14

It's not in power save mode.

I believe you said previously that you had the same phone, so you should then have a similar problem?

here in italy we don't have peloton, it's forbidden. so I can't test this case. i'm checking in your log if i can understand something more

Ah yes, I also had to buy it through the American Apple store to get it.

If I need to test something specific, let me know.

@AnneAstrid88 I guess I understood your issue, when this is happening, your trainer is streaming A LOT of data. I have some ideas how to bypass this, but let's try first disabling the debug log setting because for sure it's writing a lot, decreasing the performance.

If this doesn't help, i will do a mod trying to disabling some requests to the trainer.

Let me know how it will go

Ok I'll try that tomorrow. Thank you.
It's weird that this issue wasn't there a month ago.

I didn't change anything in the code, so it could be a patch of android that caused this for example. I have some ideas in mind to avoid this anyway

@AnneAstrid88 any news? in the mean time I created a patch for this anyway https://github.com/cagnulein/qdomyos-zwift/actions/runs/7060901858

You will see the android build in the bottom when the build is finished, i don't remember if you are in the whitelist of the non-play store version, in case not
send me an email to roberto.viola83 at gmail.com indicating this ticket Thanks

sorry this one https://github.com/cagnulein/qdomyos-zwift/actions/runs/7061057203

Yeah I checked it this morning and by disabling the debug log it was fixed.

and yes I have access to the private Beta on android.

Yes I will when the version is available :-)

It's already https://github.com/cagnulein/qdomyos-zwift/suites/18672596629/artifacts/1086434281

You need to uninstall the play store version if you want to try and send me the email to unlock it

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

I'm sorry, I didn't test it yet. I will try to do it this week.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@AnneAstrid88 any news?

I'm so sorry, I haven't tested it yet. I will test it tomorrow on my peloton ride.

I tested it and it seems to be working. However, I noticed when scrolling through the settings there was the screen was lagging and that never happened before. I wasn't running any other apps at the same time.

The lagging is not something controllable from QZ. I mean I'm trying with my pixel 6a and it runs smooth. The settings page could be improved for sure, trying to add some subpages in order to reduce the size of the main one

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.