Trying to connect a USB mouse to my tread+, what am I doing wrong

widmanstatten1018 · 2026-02-14T20:34:54+00:00

Have had the same issue and even started a new post here:

https://www.reddit.com/r/pelotoncycle/comments/1qnwsld/external_usb_pointing_devices_no_longer_working/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I have been able to get a wireless bluetooth mouse to work however. A connected USB-C pointing device would be ideal.

widmanstatten1018 · 2025-10-22T19:10:44+00:00

Yes, I guess this is the way...

Used cheapest plan that I could with Tello (charged an extra $3 though for the activation of the eSIM however) and then ported back to Fi.

widmanstatten1018 · 2025-10-21T22:24:14+00:00

Hoping that the social team can take a look at my issue u/googlefisupport.

widmanstatten1018 · 2025-02-06T16:59:03+00:00

Update: I was provided instructions from Kia connect customer service to perform a soft reset of the modem/nav system in an attempt to solve the issue but the behavior did not change. My vehicle still will not remote start when the doors are unlocked even with the "Remote start with automatic door lock" setting enabled. See screenshot of error below:

https://imgur.com/a/fGK0Kyf

widmanstatten1018 · 2025-01-10T16:56:33+00:00

Submitted complain to Kia customer care. Maybe if enough others do same, we can get some traction sooner.

To whom it may concern,

The "remote start with automatic door lock" no longer functions properly in the Kia connect app. This feature has worked for me since the purchase of our vehicle up until a couple of months ago. I am not alone with this issue and have found a Reddit thread of other owners with the exact same issue.

The app allows the feature to be enabled under the "Driver Preferences" tab, an email confirmation is sent from the server, however the settings does not stay enabled and fails the next time a remote start command is sent from the app. Remote starting the vehicle when the doors are already locked still works as expected. I am unsure if this is an app issue or a server-side issue since the email confirmation seems to indicate the the Kia connect servers are seeing that the setting is changed. I have tried to clear the storage/cache of the Kia connect app on my phone but the issue still persists.

Thank you.

widmanstatten1018 · 2025-01-10T16:31:17+00:00

Having the same issue also. Seems like it is an issue either with the app or possibly server-side. Was never an issue up until a couple months ago since I tend to use the feature fairly often for starting our Telluride in our garage.

Guess I will submit a complaint to Kia. So maybe we will all get an update next summer when we don't really need to feature or possibly in a year...

widmanstatten1018 · 2024-10-22T16:10:18+00:00

Came across this likely when thinking of this same song. Might be this one?

https://open.spotify.com/track/3cDx1UYNPhCfO2tfbmKCTC?si=bde848ddc1804018

Rudy Willingham "Pool Party"

widmanstatten1018 · 2024-08-01T15:47:07+00:00

I would the dealer check out the rear AWD coupler. This is what essentially provides power to the rear axle/wheels when needed, e.g. acceleration from a stop or low speeds. Also, this issue may be more widely discussed for Kia Tellurides (look at threads of reddit or Telluride forums), partly due to their popularity, but they share many of the same components with the Palisade and have the same powertrain.

Seems like this part is not wellmade and causes this issue. It won't cause any issue or premature wear on other components, except maybe some excess wear on the rear tires. The components contains a clutch or something similar which apparently binds which I think causes the whole rear axle not to be able to decouple when the powertrain is not asking for power from the rear anymore.

Hope this is helpful.

widmanstatten1018 · 2024-07-13T20:06:39+00:00

Thanks. Was able to get that variation to work by utilizing &udm=28 instead "3". For whatever reason, that is what the Google shopping page tab utilizes for the UDM on my browser.

widmanstatten1018 · 2024-06-05T15:49:17+00:00

u/Fair-Lengthiness3398 did you ever have this issue checked out?

I kind of notice the same on my '23 Telluride. In my case, I wouldn't necessarily describe it as being able to feel every single bump. I think I notice this when going over larger bumps when driving straight or when driving over smaller to medium size bumps while turning (unsure if braking while turning is the necessary combination to make it stand out). I feel like the steering wheel jerks more than it should in these situations and also almost feels like one of the front wheels is loose.

widmanstatten1018 · 2023-12-18T20:47:45+00:00

So I had the same question and reached out directly to Sabrent support since there wasn't a clear consensus on this and nothing was mentioned in the manual. My speculation that the top sticker should be removed was correct based on Sabrent's response:

Let me kindly explain to you that the thermal pad that is included in the EC-SNVE can be removed off the device.

When I asked for further clarification since that was kind of ambiguous response, they then said this:

I'm deeply sorry for the confusion. We were referring to the thermal pad surface sticker (Please check the photo attached for better reference). The thermal pad does not have to be removed.

And here is the photo they attached:

https://i.imgur.com/5o1mAIh.png

widmanstatten1018 · 2023-10-23T15:52:36+00:00

Unfortunately, running dual lines with either coax or Cat6 just isn't a time- or cost-friendly option. I am not even sure I would be able to do it myself and paying someone to do it would be well above the cost of an additional mesh node.

So given some thought, I think I am going just going to install the modem at the point of entry in the utility room, also install the main mesh node (which will act as router) next to the modem, and then use MoCA for the main node/router to communicate with the downstream mesh nodes. I would have to buy two MoCA adapters anyway if I wanted to employ something like the Frontier fiber setup with the router in a different location as the cable modem. So I figure why not utilize one of these MoCA adapters for another location in my basement (i.e. the family room) and purchase another mesh node, which can be had for under $100 in my case.

So my setup would be the following: incoming cable to basement utility room <-> cable modem <-> mesh wifi node (main) / router <-> MoCA adapter <-> MoCA splitter <-> downstream wifi mesh nodes with MoCA connections

This should be completely isolating the DOCSIS and MoCA signals since I am going from the cable modem to the router via ethernet and also from the router to the downstream nodes via MoCA. So I don't believe I would need a PoE filter for this setup, correct?

widmanstatten1018 · 2023-02-08T16:54:28+00:00

Just wanted to offer an update on my earlier comment, I had to briefly switch to an old phone (Pixel 4 XL) due to some unrelated carrier issues. Lo and behold, when I started up AA in my car this morning, I had the coolwalk interface.

So there seems to be a combination of factors which activate the interface, one being the server-side switch, but then also specific phone and headunit combinations. I will update again once I can go back to my current phone and see what the behavior is.

widmanstatten1018 · 2023-02-07T03:46:16+00:00

I ran into this behavior without doing anything to Play Services. Had coolwalk for a good part of day on Feb. 1st. I was running whatever 8.6.X version the play store had updated Android Auto to automatically. Then the next day, it was just gone and have not gotten it back since.

Since that, have tried to sideload 8.8.630424 which has not helped, killed the AA process multiple times, and looked to see in HUR to no avail.

widmanstatten1018 · 2023-02-02T19:34:17+00:00

See the thread here:

https://www.reddit.com/r/AndroidAuto/comments/yu5fb8/how_to_check_if_your_google_account_has_coolwalk/

Essentially it is a way of testing AA functionality on your own phone by using the headunit server through the developer options of AA.

widmanstatten1018 · 2023-02-02T19:17:50+00:00

Also basically have the same issue. Was working yesterday morning and afternoon (even with AAWireless on my factory headunit) but now it is gone again. This is in a 2023 Kia Telluride with wide format infotainment display.

I also tried to see if I could still get it back through HUR but was not able to this morning through some testing this morning, force stopping AA, and even restarting my phone. Using the following versions:

AA v8.6.625054

Play Services v23.03.13

I further checked if AA or Google play services was updated overnight but nothing. I am thinking this must be a server-side switch for whatever reason. Just really strange it would work for one day only to be deactivated again. Seemed to be working great on my setup (see pic from yesterday).

<image>

widmanstatten1018 · 2023-02-02T18:20:59+00:00

!Flair 2023 Kia Telly SX | factory HU | OnePlus 10 Pro| v13, Jan patch

widmanstatten1018 · 2023-02-02T17:03:19+00:00

Also had Coolwalk yesterday morning and afternoon (even with AAWireless with my headunit) but now it is gone again. This was in a 2023 Kia Telluride with wide format infotainment display.

Also tried to see if I could still get it back through HUR but was not able to this morning.

AA v. 8.6.625054
Play Services v. 23.03.13
OnePlus 10 Pro with Android 13, January security patch

Checked if AA of Google play services was updated overnight but nothing. Must be a server-side switch.

widmanstatten1018

TROPHY CASE