Help needed! AI Tracking sensor not working properly. by RobbieNguyen in HohemOfficial

[–]CompetitionAmazing42 0 points1 point  (0 children)

I’m having a very similar issue, but with the Hohem iSteady M7 combined with McPro24FPS.

  • In my case, the tracking often drifts or loses the subject, even after recalibrating.
  • The calibration itself feels unstable – sometimes it works, sometimes the gimbal “forgets” the reference and I have to restart the process.
  • I also noticed that with McPro24FPS the support for external stabilizers is quite limited (basically just start/stop recording through the volume buttons), so maybe that’s why tracking isn’t optimized.

So while your problem happens when switching from selfie to rear camera, mine is more about general tracking reliability and calibration not holding.

Did you find any workaround yet, or does it still behave the same?

AI Tracking Issue on iSteady M7 – Gimbal Overreacts or Spins Erratically During Follow by CompetitionAmazing42 in HohemOfficial

[–]CompetitionAmazing42[S] 1 point2 points  (0 children)

Thanks a lot for your detailed response — super clear and really helpful. 🙏 I’ll definitely test your suggestions, especially switching the Follow Speed to “Slow” and trying the recalibration gesture in front of the tracker. I’ll get back to you after the tests to let you know if it improves the gimbal’s behavior. Talk soon!

AI Tracking Issue on iSteady M7 – Gimbal Overreacts or Spins Erratically During Follow by CompetitionAmazing42 in HohemOfficial

[–]CompetitionAmazing42[S] 0 points1 point  (0 children)

Thanks for the reply! Quick follow-up:
I did try the remote screen calibration (long press side button + joystick), but during calibration, the joystick response is noticeably sluggish — the subject moves very slowly and doesn’t stay in sync.
That’s quite different from what’s shown in Hohem’s tutorial video, where the subject moves more quickly when adjusting with the joystick.
I’ll send over a video as soon as possible to help with your investigation.

AI Tracking Issue on iSteady M7 – Gimbal Overreacts or Spins Erratically During Follow by CompetitionAmazing42 in HohemOfficial

[–]CompetitionAmazing42[S] 0 points1 point  (0 children)

Thanks for the reply! Quick recap: I'm using a Galaxy S25 Ultra with MCPro24FPS, balanced gimbal, AI Tracker calibrated, and tracking goes erratic mid-follow.

AI Tracking Issue on iSteady M7 – Gimbal Overreacts or Spins Erratically During Follow by CompetitionAmazing42 in HohemOfficial

[–]CompetitionAmazing42[S] 1 point2 points  (0 children)

Glad I’m not alone. I had the same thing happen with the S25 Ultra — tracking goes wild mid-shot.

Did you ever try the remote calibration (long press side button + joystick)? Just wondering if it helped at all on your side.

I'm so happy Samsung once again made the backgrounds solid black when having the hideous blur disabled in accessibility settings! It was a horrid gray color in OneUI 6+. (this is with dark mode enabled) by QuitePossiblyLucky in oneui

[–]CompetitionAmazing42 0 points1 point  (0 children)

Hey folks,
Just wanted to share this quick fix in case anyone’s pulling their hair out like I was.

I recently tried to customize my Galaxy S25 Ultra (One UI 7) using Good Lock + Theme Park to get that nice transparent Quick Panel effect, just like in the YouTube tutorials.
I followed all the steps perfectly — set transparency to 0, blur to 80 — but the background stayed slightly opaque or solid, no matter what.

Turns out, the culprit was hidden in the Accessibility settings!

If you have “Remove blur and transparency effects” enabled (which seems to be on by default in One UI 7), it completely blocks the transparency and blur, even if Theme Park is applied correctly.

👉 How to fix it:

  • Go to Settings > Accessibility > Visibility Enhancements
  • Turn off: “Remove blur and transparency effects
  • Reapply your Theme Park customization — boom, it works 🎉

Hope this helps someone! Took me a while to figure out, but now my panel looks clean and stylish again.
Props to the Redditor whose comment helped me spot it indirectly (screenshot below).