PSPilot
 New
Switzerland
Offline
|
It's a very simple matter: if you want to pair a new phone to any Bluetooth device, you HAVE TO make the device forget the old pairing (ok, there is multi-point BT, but that's irrelevant for the Osmo). If you lost the old phone to delete the pairing there you have to reset the BT pairing on the device. Either there's a dedicated custom function for that (as newer Osmos have it), or you have to completely factory reset the device which also 'kills' the pairing (mostly). Any attempt to pair an Osmo 2 with a phone while another pairing is still 'stored', HAS TO FAIL!! As long as the Osmo waits for it's paired phone, it dosn't initiate a new pairing. I can't understand, what the heck the 'administrators' here are talking about! There's no need to 'forward the issue to any engineer' ... they know it.
Surprisingly I couldn't find an obvious way to delete the pairing. No hint for such a function on the net (let alone the manual). Obviously there is no such function for the user, no factory reset either. I consider that as a BIG flaw in the design or firmware. But there is still hope  . I don't know how and why the following procedure is working, but it is. It helped me getting an old Osmo 2 connected to an iPhone 12 Pro Max on iOS 15.3.1. Maybe it's an undocumented feature, since the developers of that device needed some kind of function for that trivial task. Ok, here we go:
1) Most important, you need a micro-USB OTG adapter. It has a micro-USB plug on one end and a USB-A female (socket) on the other. These adapters exist as tiny one-piece 'thingies', or as short adapter cables. If you go to Amazon and search for 'micro-USB OTG adapter', you'll find them for very little money and see what I mean. Anyway, with that adapter and your usual USB cable for your phone, you can connect the Osmo 2 with your phone. In my case, I plugged my ordinary Apple lightning USB-cable in the adapter and had a micro-USB to Apple cable with OTG-function. Likewise you would use a micro-USB or USB-C cable instead of my lightning cable, whatever fits your phone.
2) The procedure is simple: start with the Osmo 2 powered OFF. Use the cable to connect the Osmo 2 with your phone. Go to the Bluetooth settings on your phone and that screen, where you find new devices to pair. Now power on the Osmo 2 and only a few seconds later, the Osmo 2 should appear as a new, or 'pairable' device. DON'T PAIR IT NOW! My experience is, that with the cable connected, the pairing will fail. Instead switch the Osmo 2 off again, remove the cable and then repower the Osmo 2. I personally also start that whole BT screen on my phone new, before I power on the Osmo 2 again. Especially the iPhone is kinda picky when BT devices appear and disappear rapidly in the same 'discovery session'. YMMV, but just leaving and reentering that screen once, or even power cycle the whole Bluetooth thing on the phone won't harm and you're save, that the discovery of new deivces works well.
Anyway, my Osmo 2 showed up normally in the BT screenn after that little trick, I could successfully pair it and from that point on, it worked like a charm with the DJII app. Talking of that, you don't need the DJII app for all the above. Once the gimbal is paired on your phone's BT list, start the app as usual and use it - it'll work. And as I wrote above, the app has no problems with the newest iOS versions. I can't talk about Android 12.
My conclusion is, that this OTG connection between the phone (actually a USB-host or -master) and the Osmo is resetting the old pairing. This function should be available easier for customers somehow - as it is on the newer Osmos. Maybe it even works with a simple micro-USB (Osmo) to USB-A cable to an ordinary computer or notebook. Maybe any USB-host can reset that Bluetooth pairing. But I didn't try that. I'm glad that mine works again .
|
|
lvl.3
Administrator
lvl.1
lvl.2
. I don't know how and why the following procedure is working, but it is. It helped me getting an old Osmo 2 connected to an iPhone 12 Pro Max on iOS 15.3.1. Maybe it's an undocumented feature, since the developers of that device needed some kind of function for that trivial task. Ok, here we go: