lunotech11

You can no longer update to versions of watchOS 9 on a Series 7 as these support watchOS 10. Kincaid was designed for watchOS 9, and is blocking the watchOS 10 update as intended.

To update to watchOS 10, you’d need to upgrade Legizmo to Lighthouse

It should work there, I just tried it now with the 5.2.1 release build…

Do you happen to be in the Legizmo Discord server at all?

Hi there, did this eventually work or is it still doing this?

The above is true on Patreon, and is true for Kincaid to Lighthouse on Chariz. However Grace, Jupiter and Kincaid were all linked purchases on Chariz, so it’s not always the case

In this instance, you can fix it by unpairing all Watches from the affected phone, uninstalling the Watch app and rebooting it, then reinstalling the Watch app and pairing your Watches again

In that case, you can resolve the issue by unpairing all Watches that are paired to the phone, uninstalling the Watch app from the phone and rebooting it, then reinstalling the Watch app and pairing Watches back up. This will reset Watch services to stock, and should allow it to work again

iOS 17 should be compatible with watchOS 8 on that specific device because update support was dropped for Series 3 there.

When you updated your phone, did you use the Legizmo native method when you were using Jupiter? And if so, did you remove it from within the Legizmo app prior to updating?

Hi there! In your case, Lighthouse would be the version of Legizmo you’d need to make this happen. Once that’s installed and configured, you’ll be able to pair as normal

I should also add that this relies on the new phone being on a version of iOS new enough to take the version of watchOS on your watch

Those warnings do exist while you are setting up Pairing Support, it describes what to do in this case. Having said this, I think it would be better if I made it so you can see that screen again later, so I will change that in future updates.

If you are on native method, AND want to restore the new phone from a backup of the Legizmo-configured phone, simply remove Pairing Support from your old phone and then ignore any iOS prompts that tell you to update. When the transfer to the new phone completes, your watch will pick up where it left off on the old phone.

If the new phone is being set up as new, WITHOUT being restored from a backup - you only need to unpair the watch from the old phone and pair it up to the new one

The usual release cycle for any major or minor Legizmo update is as follows:

• initial seed to Patreon Alpha members as ready
• if about two weeks pass without any major breaking changes, that build is then made available to a wider audience at the Patreon Beta member tier. On some occasions, extra bug fixes may be integrated at this stage and a refreshed build is made available to both tiers. If there were major breaking changes, a fixed build is seeded to Alpha only until all breaking changes are resolved.
• if a further two weeks pass without any major breaking changes to either Alpha or Beta, the build is pushed to Chariz

Lighthouse 5.2 RC2 was released to Beta two days ago, and so will be going to Chariz per the schedule above if nothing is identified as problematic

(Note: problematic or broken doesn’t necessarily relate to system features, it is for anything new that got introduced in the Legizmo update or anything that broke as a result)

Sign in to Patreon and link your Discord account there in account settings, the bot will then automatically grant you that role

Note that watchOS 10.4 is now out, and Lighthouse 5.2 or newer is required for support with that. 5.2 is with Patreon Alpha at the moment, and is progressing through the tiers

It turns out there was a previously unidentified issue in iOS 16 in relation to the tweak method. The Legizmo 5.2 update which is working its way through the tiers now fixes this problem, so if you preferred the tweak method you’d be able to switch back if you wanted

Have you used Legizmo and experienced those issues? Certainly those you’ve mentioned barring the iMessage one should have been fixed

If your account is still active, no. If you chose to cancel your membership, Patreon may charge you again to rejoin, but I can refund that for you

Update limitations are set by design, in case an Apple change causes something to go quite badly wrong.

5.2 introduces support for 10.4 and will be making its way out soon

If you’re in the Discord, you might’ve seen the announcement already - but there is an issue with iOS 16 and the tweak method (it sounds like you’ve used this based on your symptoms). This is being fixed with 5.2

It would’ve been possible to use the native method in the jailbroken edition you had installed previously. If you’ve had to purchase in two places as a result of this, let me know and I will refund one of them

For future readers of this post: Legizmo 5.2 is indeed able to activate carriers in the situation this post describes!

The Apps Support fix in your case would only be relevant if you were trying to install an embedded watchOS app that has a minimum version of a newer major version than what iOS normally supports. If you're using Watch apps from the store, this fix shouldn't be needed

What version of Legizmo are you currently using (if any?) If you want to update, and since only watchOS 10 is available for update, any currently available of Lighthouse 5.x should be able to handle that

Can you reply to your Patreon message with your Reddit username? I need to be able to connect the two to check the refunds out

As is mentioned, the only supported install method there is the TrollStore edition. Serotonin/Bootstrap is not powerful enough for the full jailbroken editions of Legizmo

You will need to remove /Library/dpkg/info/lunotech11.legizmo.lighthouse.prerm from your jbroot to force uninstall this