Failed to connect QZ to NordicTrack C1750 about qzcompanionnordictracktreadmill HOT 48 CLOSED

@thephatp, sorry to be late to the party. I just read through all your posts and have some suggestions. Just wondering if you did a treadmill reset before running the Windows companion install script? If so, you can also try in Developer options to select ''revoke usb debugging authorizations' and retry the script.

Regarding privileged mode timing out on you, unfortunately privileged mode is only enabled for 30 minutes after given a response code. There is a way to make it permanent which is implemented in the companion install script, but only works if you get ADB connection working. You should be able to get ADB working eventually. We just have to figure out why you're getting the ADB connection refused error.

Regarding treadmill speed and incline control, the companion uses an internal ADB connection to get this to work. Again, if ADB is refusing the connection then we need to figure out why.

from qzcompanionnordictracktreadmill.

For my TM, I cannot find a file manager that will work with Android 5.1.1, so I cannot browse files. Happen to know of a reputable site to get old APKs from?

i'm usually use this site and this file browser https://apkpure.com/it/es-file-explorer-file-manager/com.estrongs.android.pop/versions

from qzcompanionnordictracktreadmill.

I guess the android system doesn't accept adb over network. are you able to connect the usb to the treadmill?

Not yet, but I ordered a cable yesterday anticipating I might need to try this route. Should be coming today. :)

from qzcompanionnordictracktreadmill.

you need first to download the driver @thephatp
https://adb.clockworkmod.com/

then from a prompt command run

adb devices

from qzcompanionnordictracktreadmill.

@thephatp also check in the device manager, under windows settings, what the usb cable will look like (send here a screenshot)

from qzcompanionnordictracktreadmill.

@thephatp, great job trying to get this to work. The only thing I can think of is maybe the USB cable is the problem. I know some cables are power only and some are power and data, and some are data only.

from qzcompanionnordictracktreadmill.

Hi! ok so you can't control the treadmill now right from the qz app? did you set the treadmill in the qz companion settings?

from qzcompanionnordictracktreadmill.

from qzcompanionnordictracktreadmill.

Below is the text from "Dump Log" within the companion app. Note that when I logged into privileged mode (have to do that every time), and launched the companion app, it wouldn't responded and popped up the message to wait or kill. I waited, to no avail, so then I killed it and restarted, and then got this dump. Not sure if that has anything to do with the note on UDP below, but wanted to mention that, just in case.

2023-06-04 09:10:01.882 Service started
2023-06-04 09:10:01.884 Service started
2023-06-04 09:10:01.885 Service started
2023-06-04 09:10:01.886 Service started
2023-06-04 09:10:01.887 Service onCreate
2023-06-04 09:10:01.888 Service postDelayed
2023-06-04 09:10:01.888 Service started
2023-06-04 09:10:01.888 Service started
2023-06-04 09:10:01.889 Service started
2023-06-04 09:10:01.889 Service started
2023-06-04 09:10:01.89 Waiting for UDP broadcast
2023-06-04 09:10:01.895 no longer listening for UDP broadcasts cause of error bind failed: EADDRINUSE (Address already in use)
2023-06-04 09:10:02.391 Service run
2023-06-04 09:10:02.396 /sdcard/.wolflogs/
2023-06-04 09:10:02.396 lastModifiedFile /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:02.397 string: /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:02.397 Parsing /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:03.389 Service run
2023-06-04 09:10:03.393 /sdcard/.wolflogs/
2023-06-04 09:10:03.393 lastModifiedFile /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:03.393 string: /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:03.394 Parsing /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:04.443 Service run
2023-06-04 09:10:04.446 /sdcard/.wolflogs/
2023-06-04 09:10:04.447 lastModifiedFile /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:04.447 string: /sdcard/.wolflogs/2023-06-04_logs.txt
2023-06-04 09:10:04.447 Parsing /sdcard/.wolflogs/2023-06-04_logs.txt

from qzcompanionnordictracktreadmill.

FYI, I looked through the other treadmill types and noticed that "Cadenza Treadmill (Bodytone)" was selected for some reason. Would that cause problems?

nope, but did you set the Nordictrack 2950 IP setting in qz?
could you share a debug log while you're trying to change speed or inclination from qz ? https://github.com/cagnulein/qdomyos-zwift/wiki/How-do-i-get-the-debug-log-in-case-something-doesn't-work%3F

from qzcompanionnordictracktreadmill.

nope, but did you set the Nordictrack 2950 IP setting in qz?

Yes, set the IP in that field

could you share a debug log while you're trying to change speed or inclination from qz ? https://github.com/cagnulein/qdomyos-zwift/wiki/How-do-i-get-the-debug-log-in-case-something-doesn't-work%3F

Will do as soon as I'm back at home (couple of hours). Thanks!

from qzcompanionnordictracktreadmill.

ok I will probably check it tomorrow (7pm here in italy).
Let me know!
Also @victorypoint maybe you can help here while i'm sleeping :D

from qzcompanionnordictracktreadmill.

No worries. Here's the log.

debug-Sun_Jun_4_14_47_11_2023.log

I think it the order I changed things on the treadmill was:

1. Start workout (1 MHP)
2. Increase speed to 3 MHP
3. Increase inline to 2.0
4. Decrease speed to 1 MHP
5. Decrease incline to 0

After this, I tried controlling the speed and incline from the QZ app but again, no changes:

1. Increase incline
2. Decrease speed

I'm happy to try this in any particulate order you want to make the logs cleaner, or to produce more logging. Just let me know.

One other thing to note--I guess because I installed it via the web browser (b/c it wouldn't connect with ADB when running the .bat install script)--it doesn't maintain privilege mode, and it's not starting the foreground. Every time I walk away for any length of time and come back, it freezes on the "tap to continue" screen saver, and I have to enter privileged mode and start the QZ Companion app, then start the iFit app.

Is there any way (other than a successful run of the .bat script) that I can force it to stay in privileged mode and keep the companion app running in the foreground? I noticed the installation instructions for the companion app said the QZ-Companion.bat installation should make privileged mode always available, but I don't see a command in the script that does it. Wondering if I can try to execute a command to force privileged model on all the time. Is it possible ADB isn't working b/c I was trying to run it over wireless (seems Android 11+ is required for this)? Could I connect via USB and it work?

from qzcompanionnordictracktreadmill.

ok @thephatp i checked everything.
The main issue about your setup is the fact that ADB is not working. Without ADB, QZ can't force commands to your treadmill.
Unfortunately I can't guide you on a step by step about this because I never saw a Nordictrack TM by person, so you have to try to check if there is someway to do so. Maybe @victorypoint could help on this.

In the android settings of your TM, the adb check is enabled? (let's start from the basic)

from qzcompanionnordictracktreadmill.

The main issue about your setup is the fact that ADB is not working. Without ADB, QZ can't force commands to your treadmill.

I was afraid this might be the case, but wondering how 1373 was resolved when he was having the same issue. I'm suspecting maybe my version of android is too old?

In the android settings of your TM, the adb check is enabled? (let's start from the basic)

Assuming this is Developer Mode > Enable USB Debugging, then yes, that is enabled.

from qzcompanionnordictracktreadmill.

@thephatp #1373 was about reading the metrics, not control the treadmill if i read correctly.
@pbcsd had the same issue about adb
I guess adb wasn't implemented in the android version that you have on the treadmill.

The only way to workaround this, it's to discover how the nordictrack app controls directly the treadmill.
If you can collect the apk inside the treadmill, I can check it

from qzcompanionnordictracktreadmill.

Correct, I can't control my C1750 either, also, the target peloton speed/incline doesn't show on QD either if I recall correctly.

When you say "Collect the apk inside the treadmill", how does one do that?

from qzcompanionnordictracktreadmill.

When you say "Collect the apk inside the treadmill", how does one do that?

for example with the file manager inside the treadmill you can copy the apk somewhere (usb, network, ...)

from qzcompanionnordictracktreadmill.

For my TM, I cannot find a file manager that will work with Android 5.1.1, so I cannot browse files. Happen to know of a reputable site to get old APKs from?

from qzcompanionnordictracktreadmill.

@victorypoint - No worries, the fact that you and @cagnulein respond to posts at all (on a per user basis) blows my mind! :) I do appreciate any and all help you guys provide!

If so, you can also try in Developer options to select ''revoke usb debugging authorizations' and retry the script.

Tried this, but didn't make a difference. ADB connection still refused.

Just wondering if you did a treadmill reset before running the Windows companion install script?

It was factory reset when I got it, but I'm doing it again myself right now. Appears to be about a 30 minute process, so will be a few minutes. FTR, if this is the problem, I owe you guys big time for wasting your time. I know better. I followed every step to the T...except that one, because the previous owner had done it. 🤦‍♂️

There is a way to make it permanent which is implemented in the companion install script, but only works if you get ADB connection working.

Regarding treadmill speed and incline control, the companion uses an internal ADB connection to get this to work.

Gotcha

You should be able to get ADB working eventually. We just have to figure out why you're getting the ADB connection refused error.

Encouraging. Thank you so much for being willing to help!

i'm usually use this site and this file browser https://apkpure.com/it/es-file-explorer-file-manager/com.estrongs.android.pop/versions

Thanks, will try this once I get the factory reset done.

from qzcompanionnordictracktreadmill.

@victorypoint - Completed the factory reset. Unfortunately, ADB still won't connect (same target machine actively refused it error in log file).

These are my observations/steps/results:

1. Previous owner's reset included installing the updates from NT. I chose not to do that.
2. Privilege mode no longer requires submitting a pin (b/c I didn't update the system).
3. Android version is still 5.1.1
4. IP Address confirmed
5. USB Debugging mode enabled
6. ADB cannot connect
7. Tried the "revoke usb debugging authorizations" again
8. ADB cannot connect

from qzcompanionnordictracktreadmill.

@thephatp I guess the android system doesn't accept adb over network. are you able to connect the usb to the treadmill?

from qzcompanionnordictracktreadmill.

I guess the android system doesn't accept adb over network. are you able to connect the usb to the treadmill?

Not yet, but I ordered a cable yesterday anticipating I might need to try this route. Should be coming today. :)

Actually, just found one!

Anything specific I need to do to make the .bat file run over USB?

I just tried it, and it didn't work, but I'm assuming I have to change something in the batch file to not use IP address (wireless), or to mount a device, or something similar?

Also, FWIW, if we can get this working, I'm happy to update the wiki to include these caveats for users having issues!

from qzcompanionnordictracktreadmill.

@thephatp, the install script should work over USB as well with IP address but definitely try to driver @cagnulein suggested. The ADB driver that we've included with the install script is the same one that comes with the windows ADB developers kit

from qzcompanionnordictracktreadmill.

@thephatp also check in the device manager, under windows settings, what the usb cable will look like (send here a screenshot)

from qzcompanionnordictracktreadmill.

No luck. adb command shows no devices connected. Wonder if there is another setting to enable in Android. Looking online.

from qzcompanionnordictracktreadmill.

from qzcompanionnordictracktreadmill.

which is the cable? I can't see it. Maybe under serial port? check pluggin it and unplugging it and compare the device manager

from qzcompanionnordictracktreadmill.

Unfortunately, it doesn't seem to be recognizing a device is plugged in. Using a USB-A (TM) to USB-C (PC) to connect. Wonder if I should try USB-A to USB-A (don't have one). Will look to see if I can find info on how to get it to recognize the TM.

from qzcompanionnordictracktreadmill.

from qzcompanionnordictracktreadmill.

@victorypoint & @cagnulein, unfortunately, I've had no luck. I'm following this Android ADB doc, but I'm not getting any dialog to accept RSA key.

I noticed there is a setting called "Verify apps over USB" which is turned on and grayed out (cannot change it). See here:

Was hoping maybe I could disable that setting, but haven't been successful at that either.

Any other thoughts/suggestions?

I wish there was a way to root it to force some of these things, but at this point: (a) it seems as noted from the ADB documentation above, wireless adb is only available from Android 11+; and (b) since I can't get the USB port to recognize the laptop plugged in or vice versa, I'm not sure what else I can do.

According to an older C1750 manual I found on manualslib, it says: "NOTE: The USB port on the top of the console is for software updates only. Plug a USB drive into the USB port only if instructed to do so by an authorized service representative." This seems to imply I should be able to take further steps to override/update/root/etc., but not sure how I'd do that, and not finding much luck searching online. :/

Found this question about the USB port, but not a definitive answer. The important part here is that it's likely booting from an SD Card. Maybe the only way around this is to follow the procedure to replace the SD card, so that it doesn't boot to iFit, but at that point, I'm getting really into territory I'm not familiar with.

from qzcompanionnordictracktreadmill.

Unfortunately, I've not found any way to get windows to recognize the treadmill hardware via the USB port. None of the settings accessible to me in the Developer Mode seem to enable/allow this. I have no idea why that port isn't working. :(

If you have any other ideas, I'm all "ears." Otherwise, I may have to give up on this one. :(

from qzcompanionnordictracktreadmill.

Was going to check mine…but seem to be having a different issue with a white screen. Goes into screen saver mode after a while but doesn’t seem to load up the software and no ability to do anything.

from qzcompanionnordictracktreadmill.

Okay so called support. Had to tap the white screen 14 times really quickly and it brought up the code thing to get into the tablet and they then just had me reinstall the ifit software.

In any event, also on googling found this thread which had some good info in it..

https://forum.xda-developers.com/t/nordictrack-elite-9500-pro-treadmill-w-10-android-tablet.930764/page-7

though I’m not sure if it’s useful as no one seems to have been able to adb to the tablet.

from qzcompanionnordictracktreadmill.

@thephatp, great job trying to get this to work. The only thing I can think of is maybe the USB cable is the problem. I know some cables are power only and some are power and data, and some are data only.

Gotcha, I'll pay attention to that and order another one. Neither the one I have nor the one I ordered and received today worked. I'll keep you posted. Also, my Peloton bike screen decided to stop working this afternoon, so dealing with that now, too. 😩

from qzcompanionnordictracktreadmill.

@thephatp, I have a few more things for you to test to try and get an ADB connection. Just to confirm, you're using a Windows PC to run the scripts?

from qzcompanionnordictracktreadmill.

@thephatp, I have a few more things for you to test to try and get an ADB connection. Just to confirm, you're using a Windows PC to run the scripts?

Correct, but I also have a Mac if needed to try something else. I also have two different cables delivering on Thursday that are data cables to see if that makes a difference.

Open to whatever you have for me!

from qzcompanionnordictracktreadmill.

@thephatp, I have a few more things for you to test to try and get an ADB connection. Just to confirm, you're using a Windows PC to run the scripts?

Correct, but I also have a Mac if needed to try something else. I also have two different cables delivering on Thursday that are data cables to see if that makes a difference.

Open to whatever you have for me!

@thephatp, Ok, good. On your Windows PC, go into folder %userprofile%\.android if it exists and delete files adbkey and adbkey.pub if they exist. Then either run these commands from the command-line to see if you can connect ADB to your treadmill, or easier option - run QZ-Companion.bat script from the install package. Make sure privileged mode and USB debugging is enabled on treadmill first.

adb disconnect
adb kill-server
adb start-server
adb tcpip 5555
adb connect IP-address of your treadmill

Let us know if it helps.

from qzcompanionnordictracktreadmill.

@victorypoint - Unfortunately, still no luck. Here are my steps:

• Removed the two files from the .android folder as suggested
• Plugged in a new USB data cable
  • Note that Windows didn't recognize anything (neither in File Explorer, nor in Device Manager)
• Ran QZ-Companion.bat, but got the same error as noted previously ("target machine actively refused it")
• Manually ran each of the commands you listed :
  • adb disconnect -> "disconnected everything"
  • adb kill-server -> [no output provided]
  • adb start-server -> daemon not running; starting now at tcp:5037; deamon started successfully
  • adb tcpip 5555 -> error: no devices/emulators found
  • adb connect <IP> -> [same "actively refused" error]

Starting to wonder if the USB port is bad or disabled for some reason.

from qzcompanionnordictracktreadmill.

@victorypoint - Unfortunately, still no luck. Here are my steps:

• Plugged in a new USB data cable

  • Note that Windows didn't recognize anything (neither in File Explorer, nor in Device Manager)

• Ran QZ-Companion.bat, but got the same error as noted previously ("target machine actively refused it")

• Manually ran each of the commands you listed :

  • adb disconnect -> "disconnected everything"
  • adb kill-server -> [no output provided]
  • adb start-server -> daemon not running; starting now at tcp:5037; deamon started successfully
  • adb tcpip 5555 -> error: no devices/emulators found
  • adb connect <IP> -> [same "actively refused" error]

Starting to wonder if the USB port is bad or disabled for some reason.

There are a number of low cost USB testers on Amazon that you can try to see if there are any signals coming from that USB port. I bought one because it saves me so much time. No more questions if that port (or cable) is working or not.

from qzcompanionnordictracktreadmill.

@thephatp, okay thanks for trying. I assume you deleted the files I mentioned in %userprofile%.android if they existed?

My next suggestion is try over wifi again. Ensure both windows PC and treadmill are connected to the same wifi band at 2.4mhz. Make sure it's not a multi band connection e.g. both 2.4mhz and 5g or using band steering. Then try the above steps again.

from qzcompanionnordictracktreadmill.

@thephatp, okay thanks for trying. I assume you deleted the files I mentioned in %userprofile%.android if they existed?

My next suggestion is try over wifi again. Ensure both windows PC and treadmill are connected to the same wifi band at 2.4mhz. Make sure it's not a multi band connection e.g. both 2.4mhz and 5g or using band steering. Then try the above steps again.

Ugh, I missed documenting that step, but yes, I did remove the files before trying the steps. I updated the original comment to note that.

I'll try your suggestion on wifi band on Friday. That said, according to the Android documentation, it seems ADB over wifi wasn't supported until Android 11 (when Google enabled ADB OTA functionality), correct? Since I have 5.1.1, will wifi every work for running ADB commands? Like I said, happy to try it, but just wondering if that's a losing battle based on my Android version.

I'll also take @TinLe's comment about buying a port tester. Good idea and might save us some headache (while presenting others), lol.

from qzcompanionnordictracktreadmill.

@thephatp, it's a bit confusing but this article helps explain - https://developer.android.com/tools/adb#Enabling

There is Wireless debugging which is a newer feature - Android 11 (API level 30) and higher support deploying and debugging your app wirelessly from your workstation using Android Debug Bridge (adb)

Before that is USB debugging over wifi - ADB usually communicates with the device over USB, but you can also use ADB over Wi-Fi. This is supported by latest Android and lower. Typically it works by connecting via USB cable first, then disconnect cable and finish connection over wifi. Many Android devices can do this without the initial USB cable connection. I'm hoping yours can do it without cable.

from qzcompanionnordictracktreadmill.

@victorypoint, thanks for sharing that link. That renews my hope. The next thing I would suspect, in that case, is a driver issue, since Windows never recognizes the device. The article you linked has a link to Run Your App on a Hardware Device. Based on that, I'll see if I can at least establish a connection via ADB with my Mac. If no additional drivers are needed to install on a Mac, maybe I can get it to trigger something with ADB and at least see a connection established. While I know the .bat script won't work on my Mac, we'd have a little more info.

I've also ordered a USB tester, so I can check that this weekend as well.

from qzcompanionnordictracktreadmill.

@thephatp good luck. I also forgot to mention, if you get that ADB connection refused again, try toggling USB debugging off and on several times on the treadmill as you retry the connection.

from qzcompanionnordictracktreadmill.

If we could pull the apk from the tablet, would that be helpful? Any idea where one would look and/or would the file name or extension have apk in it so might be easiest to search?

from qzcompanionnordictracktreadmill.

If we could pull the apk from the tablet, would that be helpful? Any idea where one would look and/or would the file name or extension have apk in it so might be easiest to search?

we can try to disassemble it but it will be an hard job

from qzcompanionnordictracktreadmill.

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.

from qzcompanionnordictracktreadmill.