[BUG]Unexplained crash #2305
Comments
|
do you also send the crash report when the iphone asked?
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno mer 24 apr 2024 alle 20:09 Eric McMurry ***@***.***>
ha scritto:
… Assigned #2305 <#2305>
to @cagnulein <https://github.com/cagnulein>.
—
Reply to this email directly, view it on GitHub
<#2305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWD3MVKRXNBFEI3DYYLY67YN7AVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGU4TMMJZHAYDKMQ>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
crash at 11:41? there was a bluetooth disconnection of your elliptical
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno mer 24 apr 2024 alle 20:11 cagnulein ***@***.***> ha
scritto:
… do you also send the crash report when the iphone asked?
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno mer 24 apr 2024 alle 20:09 Eric McMurry <
***@***.***> ha scritto:
> Assigned #2305 <#2305>
> to @cagnulein <https://github.com/cagnulein>.
>
> —
> Reply to this email directly, view it on GitHub
> <#2305 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAALYWD3MVKRXNBFEI3DYYLY67YN7AVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGU4TMMJZHAYDKMQ>
> .
> You are receiving this because you were assigned.Message ID:
> ***@***.***>
>
|
|
it didn't ask to send the crash report. Perhaps it is one of these: clock time, the crash should have been around 11:06 I think. 11:40 would be when I finished the run after restarting it |
|
so the debug log that i need is the previous one, the one with the crash. i
will check on test flight if there is a crash
how often do you use qz? is it your first crash?
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno mer 24 apr 2024 alle 20:18 Eric McMurry ***@***.***>
ha scritto:
… it didn't ask to send the crash report. Perhaps it is one of these:
qdomyos analytics.zip
<https://github.com/cagnulein/qdomyos-zwift/files/15098698/qdomyos.analytics.zip>
clock time, the crash should have been around 11:06 I think. 11:40 would
be when I finished the run after restarting it
—
Reply to this email directly, view it on GitHub
<#2305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWDWORGBHYTTN2DWVMDY67ZPNAVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVGU2TONRTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
yep, sorry about that, didn't dig into it enough. here are the logs for up to and after the crash. I use it a couple of times a week and it has crashed before, but not in the middle of a run. that has happened before while trying to get all of the pairings going. |
|
i will deeply check the log tomorrow but i have already found an issue on
your setup: since you have a bike and a elliptical on the same room you
have to force qz to connect to one or another. do it set the manual device
in the advanced settings. it should also fix your crashes
let me know
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno mer 24 apr 2024 alle 20:33 Eric McMurry ***@***.***>
ha scritto:
… yep, sorry about that, didn't dig into it enough. here are the logs for up
to and after the crash.
Archive.zip
<https://github.com/cagnulein/qdomyos-zwift/files/15098890/Archive.zip>
I use it a couple of times a week and it has crashed before, but not in
the middle of a run. that has happened before while trying to get all of
the pairings going.
—
Reply to this email directly, view it on GitHub
<#2305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWGKPYFVFYMBN6MABTTY673HBAVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVGU4DENJXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
thanks for the pointer. I usually have that setting on but I do recall I had turned it off at some point before while going through the pairing dance. I will keep it turned on. |
|
got the issue! it was a malformed packet from the elliptical that caused this. I'm fixing right now! |
|
Cool. That doesn’t surprise me, the sw on this elliptical seems like it could use a bit more testing.
Thanks!
… On Apr 25, 2024, at 01:03, Roberto Viola ***@***.***> wrote:
got the issue! it was a malformed packet from the elliptical that caused this. I'm fixing right now!
—
Reply to this email directly, view it on GitHub <#2305 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ2NDX343HGGS4ZAMXJWQVTY7CME5AVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZWGQZTGOJXGI>.
You are receiving this because you authored the thread.
|
|
Did you get the new version? Some users are struggling with testflight
these days
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno gio 25 apr 2024 alle 15:08 Eric McMurry ***@***.***>
ha scritto:
… Cool. That doesn’t surprise me, the sw on this elliptical seems like it
could use a bit more testing.
Thanks!
> On Apr 25, 2024, at 01:03, Roberto Viola ***@***.***> wrote:
>
>
> got the issue! it was a malformed packet from the elliptical that caused
this. I'm fixing right now!
>
> —
> Reply to this email directly, view it on GitHub <
#2305 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AJ2NDX343HGGS4ZAMXJWQVTY7CME5AVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZWGQZTGOJXGI>.
> You are receiving this because you authored the thread.
>
—
Reply to this email directly, view it on GitHub
<#2305 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWGZWOXKYEATV3HVWATY7D55DAVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGE2DCNBRGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I have it. It launches at least, but I haven’t tried it with the elliptical yet. Thanks!
… On Apr 25, 2024, at 08:10, Roberto Viola ***@***.***> wrote:
Did you get the new version? Some users are struggling with testflight
these days
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno gio 25 apr 2024 alle 15:08 Eric McMurry ***@***.***>
ha scritto:
> Cool. That doesn’t surprise me, the sw on this elliptical seems like it
> could use a bit more testing.
>
> Thanks!
>
>
>
> > On Apr 25, 2024, at 01:03, Roberto Viola ***@***.***> wrote:
> >
> >
> > got the issue! it was a malformed packet from the elliptical that caused
> this. I'm fixing right now!
> >
> > —
> > Reply to this email directly, view it on GitHub <
> #2305 (comment)>,
> or unsubscribe <
> https://github.com/notifications/unsubscribe-auth/AJ2NDX343HGGS4ZAMXJWQVTY7CME5AVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZWGQZTGOJXGI>.
>
> > You are receiving this because you authored the thread.
> >
>
> —
> Reply to this email directly, view it on GitHub
> <#2305 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAALYWGZWOXKYEATV3HVWATY7D55DAVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGE2DCNBRGU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
—
Reply to this email directly, view it on GitHub <#2305 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJ2NDXYVWOCDLS3Y5SHC3WLY7D6ENAVCNFSM6AAAAABGXM6A6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZXGE2DKMZWGY>.
You are receiving this because you authored the thread.
|
|
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. |
|
@realericmc any news? |
|
hi @cagnulein. I think we're all good. we had a lot of threads going and this was probably answered in one of the others. sorry about that. The last version seemed to work fine and didn't crash. thanks! |
|
Perfect, thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Apologies, but I don't know what precipitated the crash. I was a bit over an hour and 9 minutes into an elliptical session when it went down, and multiple repairing and restarts were needed to get it working again.
To Reproduce
Sole E35 elliptical (2023 version)
polar heart rate strap connected to E35 (and to kickr headwind)
qdomyos running on iPhone 15 pro max running iOS 17.4.1
zwift running on iPad Pro M2 running 17.4.1
qdomyos paired to zwift using virtual wifi for cadence, speed, and heart rate
Expected behavior
no crash :-)
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Append a debug log
debug-Wed_Apr_24_11_18_36_2024.log.zip
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: