BMPCC4K Control app - URSA Mini Pro G2

Project history

  1. Previous project: LPG/CNG Price Reporter
  2. old posting BMPCC4K can select 4K and 4.6K resolutions
  3. current posting
  4. next step
  5. Next project: designing a chain link tool library

Finally a user sent me the idenfification string for the URSA Mini Pro G2.
Blackmagic does not document the exact strings the cameras use in Bluetooth to identify themself.

I added support for the G2 to behave just like the URSA Mini Pro in the latest Beta release.



    BMPCC4K can select 4K and 4.6K resolutions

    Project history

    1. Previous project: LPG/CNG Price Reporter
    2. old posting BMPCC4K app gets presets
    3. current posting
    4. next step: BMPCC4K Control app - URSA Mini Pro G2
    5. Next project: designing a chain link tool library

    In firmware 6.3 Blackmagic finally offers a way to select the different 4K and 3K/4.6K(UMP only of cause) resolutions via Bluetooth.
    So I'm about to add these to my "BMPCC4K control" app.


    Update (2019-06-17): I tried it with the BMPCC4K and firmware 6.4 and it didn't work. I'm in contact with Blackmagic. My suspicion is that this was only rolled out for the URSA and not the BMPCC4K yet.

    Get Support

    If you have any issues with the app, please contact me using the email address mentioned in the Play Store. If you don't speak up, I can't help you.
    Also, reviews in Play Store are not a chat. They are product reviews. Not a place to ask questions and expect an answer.

    Connection Issues

    If you can't get a connection via Bluetooth or can't find your (already paired) camera, it's often a crappy Bluetooth Stack in your phone.
    In that case rebooting the phone is your best hope. Bluetooth and especially Bluetooth Low Energy is not Googlen's or most manufacturer's highest priority when it comes to Android. The API to access BLE is already pretty crappy compared to most other Android APIs and the underlying implementation is grown as more and more things have been added to the different versions of the Bluetooth standards. All of these versions the phone has to support at the same time. Nothing an app can do about that. Only Google and the phone manufacturer can fix their bugs and I can fix mine.


    On a positive note, there is still not a single crash or "application not responding" automatically reported in any version of the app installed via Play Store since late 2018.



      BMPCC4K app gets presets

      Project history

      1. Previous project: LPG/CNG Price Reporter
      2. old posting New BMPCC4K firmware - this time with BRaw
      3. current posting
      4. next step BMPCC4K can select 4K and 4.6K resolutions
      5. Next project: designing a chain link tool library

      I did not have much time to do anything on my BMPCC4K Camera Control - Android App lately but I did manage to publish a new, public beta version today that has a new tab for storing and recalling the current camera settings as presets.

      My camera is currently used on a film set, so it will take me until at least next week to properly test this Beta to offer it as a stable release.



          New BMPCC4K firmware - this time with BRaw

          Project history

          1. Previous project: LPG/CNG Price Reporter
          2. old posting New BMPCC4K firmware
          3. current posting
          4. next step: BMPCC4K app gets presets
          5. Next project: designing a chain link tool library

          Again we get a firmware update (6.2) for the Blackmagic cameras.
          This time it finally includes the BM-Raw support.
          However they had to remove the support for Cinema-DNG.

          I'll add the ability to select BM-Raw to the BMPCC4K Camera Control - Android App at once.

          Update: The new Android app is released

          However there is one issue. There is no way to determing what the camera supports.
          This was already the case with the supported resolutions on the URSA Mini Pro.
          So either I add BMraw and drop CDNG and cameras with older firmwares will loose the ability to have Cinema-DNG selected or add both and on older and newer camera firmware's there will be unsupported but selectable options.
          Here's the answer from Blackmagic:

          Hi Marcus,Unfortunately there is no facility to read back the Camera version with the Camera Control protocol, as such it is not possible to determine whether Cinema-DNG is supported or not. I have put in a change request to add this feature in a future release, but this doesn't help you with this request.Kind Regards(name redacted)
          I'll also see if 4K and 4.6K  resolutions can not be set via Bluetooth. The protocol documentation is still in a state of October last year, so new constants are defined  for these resolutions but I can guess and try.


          • I am offering the app at half the price for a week only (until 2019-03-08). Including all future updates.
          • There has not been a single crash and not a single "application not responding" since as far as Google Play Store can go back and not a single one in the last 2 app versions ever.


          New BMPCC4K firmware

          Project history

          1. Previous project: LPG/CNG Price Reporter
          2. last step: Mysterious crash
          3. current posting
          4. next step: New BMPCC4K firmware - this time with BRaw
          5. Next project: none

          Looks like there is a new camera firmware for the Blackmagic Pocket Cinema Camera 4K.

          Since the Bluetooth protocol I used to write my "BMPCC4K Camera Control" Android app did not support some features of this camera yet. I'll give it a try and see what has improved....

          Stay tuned!

          Stable Releases:

          Open Beta Test: (early access to improvements)


          New phone - Blackview BV9600 Pro

          Actually I wanted the Blackview 9600 Plus (fingerprint reader in the screen) and backed the Kickstarter compaign.
          But that was stopped and I was given the choice of getting a BV 9600 Pro or a BV9700 Pro (Much smaller battery, smaller display, IPS instead of Amoled, higher clocked CPU).

          I have chosen the BV 9600 Pro.
          It shipped with an Android 8.1 image  ("BV9600Pro_S70_V1.1_20181105V31").
          For all software issues. That's the firmware I'm talking about.


          • Battery runtime is as advertised. Without SIM card after 24h intense use (reinstalling 140 apps) and sleep tracking, it was still at 50% 
          • At some point it is supposed to get an Android 9.0 or 9.1 update.
          • It has working Qi wireless charging (lacking on my previous phone).
          • It has the same 12V 1.5A and 9V 2A quick charge as my previous phone.
          • It has NFC (also lacking on my previous phone).
          • It's a roughed IP68 outdoor phone and even compes with a hook to attach a strap for not loosing it. So it needs no Otterbox or other case.
          • SIM card can be removed without any special needle or other tools and without disassembling any case.
          • Bluetooth Audio with my Renault/Dacia MediaNav works agian (failed on the last 2 generations of phones I had)
          • The supplied contacts app is not limited to only create contacts in the address book of the first of 2 Google accounts.


          • The socket IS NOT USB-C. It's requires special 8mm plugs and standard 5mm USB-C cables don't fit!!! Obviously this is a MAJOR, MAJOR issue!!!
          • The menu/overview -button (square)  DOESN'T WORK. You can't switch between apps with the stock or any 3rd party launcher.
          • The Android Multi-User feature has been disabled (present since Android 4.4) .
          • It comes with a screen protector that is very hard to attach because of the raised display bezel. 
          • After 2 days I still can't post in the Blackview User Forum to find a solution about any of my software issues. The first post of any new user must be vetted by an admin and that still hasn't happened.
          • Some system menus have translation errors. Others are hard to understand after translation into German or UK English or US English
          • The supplied phone app is in no way integrated with the supplied contact app. A phone number can not be added to an existing contact and a contact has no long-press menu to open them for editing.


          • Back and Menu are reversed compared to my last phone
          • The default icons (including all settings items) and the wireless charger are a terribly over-the-top super-bling rose-golden colour.


          Parametric wire dispenser

          At the moment Youmagine is pretty much broken in Firefox and in Chrome due to the choice of company they got their SSL certificate from.

          However I still published a new accessory for my soldering workspace.
          A simple wire dispenser that with parameters for the number and size of spools.


          Mysterious crash

          Project history

          1. Previous project: LPG/CNG Price Reporter
          2. last step: Android App for Blackmagic Pocket Cinema Camera 4K
          3. current posting
          4. next step: New BMPCC4K firmware
          5. Next project: designing a chain link tool library

          The BMPC4K app I wrote has exactly 1 crash on 2 devices in Play Store.
          However I'm completely puzzled by the stacktrace.
          It's not made easier by the fact that I can't reproduct the crash since it happens on 2 user's phones that I have no access to.

          All my own code is in the biz.wolschon... -packages.
          This crash is entirely in the Wear OS library by Google.
          I'm using
          implementation 'com.google.android.gms:play-services-wearable:16.0.1'

          16.0.1 is indeed the latest and greatest version available at this time.
          Since Google has obfuscated it's libraries, a search for other people with this issue in that line of code turns up nothing.

          It seems to happen at Fragment -creation time. However I'm not using any fragments from GMS. At least I'm not aware of any.
          All I can try is to move from the support library 27.1.1 to 28.0.0 with a 28 target SDK. This mandates some unrelated changes. None of them look like they should affect me.

          Update: I just came back, tested that the new, public beta version works and uploaded it to Play Store. Let's see if the crash still happens and if so, something shows up in the Stacktrace that hints to a cause this time.