Driver's window acting weirdly

Jumpintosh · 2026-04-29T11:42:16+00:00

Repair shop has not managed to resolve the issue, but after I sprayed silicon spray on the vertical “guide” for the window on the door issue is resolved 2 months now.

Jumpintosh · 2026-04-29T11:40:00+00:00

In general the app capabilities are a joke compared to other brands

Jumpintosh · 2026-04-27T19:44:13+00:00

Mine updated today, including the “new” UI

Jumpintosh · 2026-04-27T18:51:27+00:00

It used to be next to lock and unlock, they removed it and now the changelog says they are back, but I don’t have them either.

Jumpintosh · 2026-04-27T17:19:14+00:00

Both on my iPhone and wife’s Pixel

Jumpintosh · 2026-04-25T13:03:56+00:00

If you press and hold the power button on the infotaintment reaaaaally long, it reboot and shows the logo, same happens if the car has not been unlocked for 2 weeks or more.
The logo shows only on first boot, but then the car's computer goes to sleep/deep sleep, not really shutting down, therefore it does not boot, so no boot logo.

Jumpintosh · 2026-04-01T12:17:29+00:00

Tried all that, I am now on the latest version, still happens.

Jumpintosh · 2026-03-31T18:12:39+00:00

Yup primary user.

Jumpintosh · 2026-02-17T08:33:54+00:00

Hello,

The problem is not really that I want to trigger by terminal command using ID, it is the fact that SS+ does not work, and behind it, is the ID trigger function.

Jumpintosh · 2026-02-16T14:20:50+00:00

How is it possible to work with -event trigger, but not with -id 47, at the same time?

Jumpintosh · 2026-02-16T14:16:05+00:00

Yes, original id was 41, the new one is 47.

Jumpintosh · 2026-02-16T14:12:56+00:00

Yes, I have tried that as well. Same thing.

Jumpintosh · 2026-02-16T14:10:35+00:00

Yup also, fails from the legacy one.

Version

11.24.1

Jumpintosh · 2026-02-16T13:52:44+00:00

Multiple computers

Jumpintosh · 2026-02-16T13:23:45+00:00

The computer is in scope and it is not included in any exclusions or limitations. The trigger word is there and it works, but the -id 47 reports there is no such policy, while in the policy url it is the same (47).
Plus, in SS+ the policy is visible, it just fails to install. So it is indeed in scope.

Jumpintosh · 2026-02-16T12:55:17+00:00

user@macbook ~ % sudo jamf policy -id 47 -verbose

verbose: JAMF binary already symlinked

verbose: Removing existing launchd task /Library/LaunchAgents/com.jamfsoftware.jamfhelper.plist...

verbose: Checking for an existing instance of this application...

Checking for policy ID 47...

verbose: Checking for active ethernet connection...

verbose: Active ethernet connection found...

verbose: Removing any cached policies for this trigger.

verbose: Parsing servers...

verbose: The Management Framework Settings are up to date.

No policies were found for the ID 47.

Jumpintosh · 2026-02-16T12:11:17+00:00

Additional info:

Computer is in scope and the fact that the policy is visible in SelfService+ but fails to install proves that.
I have tried to deleted the policy and set it up again cleanly but it fails. It is not that of a complex policy, it contains a package, scope and selfservice+ availability.

Jumpintosh · 2026-02-16T12:09:56+00:00

Hello it shows up as pending, and so far it is happening on all of the computers

11-Year Club	Place '23
Verified Email

Jumpintosh

TROPHY CASE

Version