[BUG] QZ crashes on Android when QZ Nordictrack Companion app installed on S22i #2997
Comments
|
Can you try this build https://github.com/cagnulein/qdomyos-zwift/actions/runs/12624289815/artifacts/2388242705 Google is very slow in these days, reviewing the app on the store, even the beta ones. For this reason, in order to check right now if the patch that I did is right, you can use the android build in the link (check at the bottom of the page in about 1 hour). In order to test it you need first to remove the current QZ version on your phone, install the one that you downloaded. |
|
Thanks Roberto. The new build didn't crash and did relay speed / cadence information from bike to the app. When I press incline or resistance +/- in QZ it doesn't change on the bike, but when I change resistance/incline on the bike it does reflect properly in the app. Is this by design or am I missing something config-wise? Can/will Zwift update those automatically as I ride? Also, not sure if this is a bug or just a side-effect of it being a trial version, but changing any of the Experimental Features from default (including debug logging) resulted in the app freezing on the "intro" screen (the screen with your disclaimer and troubleshooting items). Required an uninstall/reinstall to access the menu again. |
That's great!
It can be done in first version of ifit I don't know if it's possible anymore. Are you able to connect with adb to the bike?
Are you sure about this? Maybe you are changing something else in the same session? |
Yes I can. I was able to use adb to install the companion as well. I did a factory reset of my bike yesterday. Before the reset it had updated to what I believe is iFit 2.0. UI was completely different from early last year. After the factory reset it has gone back to looking like 1.x despite the bike telling me it's fully updated. Not sure why this is. At one point I loaded the iFit Admin app and clicked the "Enable iFit 2.0" at the bottom of the screen but it just took me back to what looked like iFit 1.x and said it was up to date.
I'm testing things to try and pinpoint exactly what the behaviour is. Here's an example:
App runs as expected (although bluetooth device line in the UI just says "Connecting..." constantly, but tile values update properly).
When app starts up, it freezes quite a bit. May take abnormally long to get to the tiles screen. When tiles are up it may show a "snapshot" of speed/cadence etc values but they don't update at all despite how fast/slow I pedal. It may update the values after a minute or so, but again like a snapshot, not a consistent real-time series of changes. The same will occur if I do it the other way around. Enable Debug Log, reload app, update TDF Companion IP. |
|
Ok so it doesn't go into the "intro" mode.
Are you able to send me the debug log?
With and without changing anything in the experimental settings?
I mean the metrics are working fine on the first boot of qz or so you have
the same issue?
Are you still able to go into adb now for example for getting logs? If so
we can force also resistance in this way
Roberto Viola
Software engineer and open source enthusiast
http://robertoviola.cloud
Il giorno lun 6 gen 2025 alle 21:46 Trevor Stevenson <
***@***.***> ha scritto:
… It can be done in first version of ifit I don't know if it's possible
anymore. Are you able to connect with adb to the bike?
Yes I can. I was able to use adb to install the companion as well.
I did a factory reset of my bike yesterday. Before the reset it had
updated to what I believe is iFit 2.0. UI was completely different from
early last year. After the factory reset it has gone back to looking like
1.x despite the bike telling me it's fully updated. Not sure why this is.
At one point I loaded the iFit Admin app and clicked the "Enable iFit 2.0"
at the bottom of the screen but it just took me back to what looked like
iFit 1.x and said it was up to date.
Also, not sure if this is a bug or just a side-effect of it being a trial
version, but changing any of the Experimental Features from default
(including debug logging) resulted in the app freezing on the "intro"
screen (the screen with your disclaimer and troubleshooting items).
Required an uninstall/reinstall to access the menu again.
Are you sure about this? Maybe you are changing something else in the same
session?
I'm testing things to try and pinpoint exactly what the behaviour is.
Here's an example:
1. Clear app cache/data.
2. Load app, say no thanks to the wizard, and immediately update TDF
Companion IP in settings
3. Restart app when prompted
App runs as expected (although bluetooth device line in the UI just says
"Connecting..." constantly, but tile values update properly).
4. Go back into settings, enable Debug Log
5. Restart app when prompted
When app starts up, it freezes quite a bit. May take abnormally long to
get to the tiles screen. When tiles are up it may show a "snapshot" of
speed/cadence etc values but they don't update at all despite how fast/slow
I pedal. It may update the values after a minute or so, but again like a
snapshot, not a consistent real-time series of changes.
The same will occur if I do it the other way around. Enable Debug Log,
reload app, update TDF Companion IP.
—
Reply to this email directly, view it on GitHub
<#2997 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALYWAJWLI5SM7PDXBBM2D2JLTTLAVCNFSM6AAAAABUWDD5FKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTHA4TOMBWGY>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
I've played around with it more and I can confirm that the build you sent me here is working properly. Unsure why I was having the freezing issues from earlier, but it could be due to turning on debug logging, or some unknown user error on my part. I also got the +/- buttons working for the incline after turning on the on-screen controls during the manual workout mode. I assume the feature simulates a touch on the screen to manipulate incline/resistance. Unfortunately it wasn't working for the resistance controls. Perhaps the coordinates were off for that one? I tried both "s22i" and "s22i (NTEX02121.5) settings in the QZ companion app. I have the NTEX02121.9 model. Unsure if that would make a difference. EDIT: Again you can ignore. Seems it will take Incline or resistance into consideration but not both. When I enable the "Use Resistance instead of inc." setting, the buttons in the app properly set my resistance. Leaving the comment here in case someone else has the same question. |
|
Yes I implemented inclination only because inclination handles directly inclination and resistance both |
Description
the QZ app on my phone will crash within 1-2 seconds of loading when the QZ Nordictrack Companion app is installed on my S22i (NTEX02121.9). It appears to crash as it's discovering Bluetooth devices.
Settings
Bike Options:
-- Proform/Nordictrack Options -- TDF Companion IP: 192.168.2.x (network reserved IP of S22i)
Experimental Features:
QZ Companion App set to either S22i, S22i NTEX02121.5, or Other
Noted Behaviour
App will not crash when any of the following is true:
App will crash when:
Smartphone (please complete the following information):
Debug log attached
debug-Mon_Jan_6_12_11_12_2025.log
The text was updated successfully, but these errors were encountered: