Future of the xdrip miband project


I’ve decided to improve miband integration, and change the method which was used to represent glucose data for MiBand4. Instead of the date modifying and using a custom watchface which interpreter a custom date format in correct way, i will generate entire watchface with a dynamic background and upload this watchface to the band. By using this method, all the disadvantages of changing the date on the watch will disappear, and your watch will be fully functional. So it would be possible to use it with any program, and all band features like weather, music control, fitness progress, and more would work.

In addition, this method allowing to display any data on the watch screen.

Upd. 29.01.2020

I’ve finished a new xdrip version . Would be grateful if someone can help to test it on different miband versions.

If this version would be stable, i’ll create a pull request for the official Xdrip apk version. So there would be a chance this patch would be added to the official aplication.

Upd. 29.04.2020

Great news! The pull request was recently approved and merged into official xdrip application. At the moment it is available in the latest nightly build xdrip version which can be downloaded from the following URL https://github.com/NightscoutFoundation/xDrip/releases

New watchface legend

Since v0.2.3 it is outdated watchface view

Real view on miband4 and v0.2.4 with enabled graph and bolus

Configuration tutorial by steps for v 0.2.x and higher

1. Obtaining auth key

If you want to use xdrip with Mi Band4, Mi Band5 or Amazfit Band5, you need to get Mi Band Auth key (for MiBand2 and Miband3 devices, you can skip this step). The Auth key can be obtained with these simple steps (was copied from https://www.freemyband.com/ )

  1. Unpair band from the existing official app
  2. Uninstall official app
  3. 1. For MiBands. Download and install the modified Mi Fit application
  4. 2. For Amazfit. Download and install the modified Zepp application
  5. Login into the Mi Fit(or Zepp in case of Amazfit) with your email account
  6. Pair the band
  7. Enable band visibility in the MiFit(or Zepp) settings. If you don’t have this option, make sure you have set your age in the account to be over 18 years old.
  8. (optional) Now you can uninstall modified Mi Fit (or Zepp) application and install official application or any other APK you like to use together with MiBand. If you would use official Mi Fit(or Zepp) application, you would need to Login into the Mi Fit(or Zepp) with the email which was used with the patched application.
  9. Finished! You can find your Auth key on /sdcard/freemyband folder of your phone

Notice

1. If you reset (MAC address of band change) or unpaired your band, the Auth key need to be calculated again. The miband will change the MAC address, so you should change mac and auth key in xdrip(for auto search you can clear mac address and auth key fields)
2. The modded mifit apk is compatible with any firmware version installed on your band
3. You can do this procedure with any phone (if your phone doesn’t allow install apk outside Play Store, you can ask your friend to obtain this auth code for you)

2. xdrip configuration. Connecting to miband

  1. If you have original xdrip application installed on your phone, you would need to delete it. To save all your existent settings and glucose history, you can export your current database into file. To do this, click to the 3 dots on the main xdrip screen, select Import/export feature -> export database.
  2. Install latest patched xdrip from this link xdrip-miband. If you had a database backup, you can restore it by using export/import feature mentioned earlier.
  3. If you skipped “Obtaining auth key” phase (only for miband 2 and 3), go to MiFit settings, and enable band visibility.
  4. Place miband near the phone.
  5. Go to xdrip Settings -> Smart watch features -> MiBand and enable option “Use MiBand”  for both MiBand and Amazfit.
  6. Normally miband should be automatically found, and you will see a notification with your model name. If this happen, you can skip next step.
  7. If it wasn’t found automatically, make sure the band visibility option was enabled in MiFit, then disable “Use MiBand” option and repeat step three. You can also enter the mac addres manually (in this case, there no need for visibility option enabled).
  8. Now the miband should be connected, but it is required authentification. On MiBand2 and MiBand3, you should approve authentification by touching the miband button. For MiBand4, MiBand5 or Amazfit Band5 you don’t need to do anything. Normally auth key should be automatically extracted from the file /sdcard/freemyband which was generated by patched Mi Fit(or Zepp) application. But if it was not generated, you should manually enter the key in “Auth key” field and retry everything from step 4.
  9. Finally, you should see the message that your device was successfully authenticated.

3. xdrip configuration. General settings and installing glucose watchface

3.1. Configuration for MiBand4, MiBand5 or Amazfit Band5

Upd (30.12.20 )The “BG readings as notification” was removed in Ver 0.3.2 (09.09.2020) So now For MiBand2 and 3, the readings would be sent as notification. For MiBand4,5 and Amazfit Band5 would be used watchface uploading.

If you use a MiBand4, you can receive a glucose readings in two ways

  1. In standard miband way by using the text notifications
  2. Displaying glucose values on the main band screen with help of dynamical custom watchface..
  1. When use a text notification, xdrip would send a message to the miband after every glucose reading.
  2. When use a “dynamical custom watchface” the xdrip will generate a new watchface after every reading and will send this watchface to the miband. This option available only for MiBand4. All miband features would work as before. The watchface with required measurement units (mmol or mg/dl ) would be automatically installed. It would use the units from the general xdrip settings.

The option “BG readings as notification” in MiBand settings allow to controll the way you prefer to receive glucose values. When it is enable , you would receive notifications after every glucose readings. And when it is disabled, this fancy “dynamical custom watchface” would be used.

You can also enable option Send alarms to receive glucose low/hight alerts. If you enable this option, you would get bg alerts as a phone call. Instead of the caller number, you would see an alarm text with the current glucose value. During alarm notification, it is possible to push on the ignore button on you band to skip alarm or push on hangup button to snooze alert. The low/high alarms can be configured directly in xdrip general settings

It is also possible to enable night mode feature (in miband screens/ features menu) This feature allow to decrease glucose synchronization interval by specifying interval value and mode start/end time. This mode allow to improve miband battery life by reducing synchronization frequency.

Since v 0.2.4 it is possible to display bolus on the band (if this information present in xdrip). The bolus data can be displayed only when graph option enabled.

Finally to send reading to the see miband you should enable “Send reading” option

Notice

1. Keep your watch nearby with your phone, while phone transmitting data (actually the real BlueTooth connection distance can be even up to 50 meters 🙂 ) If your band will lost connection with the phone while transmitting watchface, it will automatically will use default watchface. This watchface would be replaced again after connection would be established
2. Take a note to the bluetooth connection status and last synchronization date to make sure you see not outdated data. Always remember to
3. The band will not accept a new watcface if battery level is less then 10%. In this case the band will automatically switch to notification mode.

3.2. Configuration for MiBand2 and 3

The only possible way to receive bg values on these band versions is to receive them as a text notification. Such notification would be sent to miband after every reading.

Xdrip miband integration apk changelog

If you like this project and want to thank an author for work done or want to support further development of features, become a sponsor on Patreon

If you have some advices regarding features that you want to see, or want to see similar feature on some specific band type, please write them in the comment of the donation form.

The latest xDrip version can be found here

Ver 0.2.4.1 (15.03.2020)

  • Fixed App Crash at the settings screen on the first run.

Ver 0.2.4 (10.03.2020)

  • New. Added option to display bolus (when enabled graph)
  • Fixed issue with when BG numbers were displayed without infill
  • For better readability, BG number size was slightly increased
  • Added bg prediction line on the graph (would display 30 minutes prediction line)

At this moment, most of the issues were fixed, and i added many new features so I hope this would be the latest version 🙂 I have plans to merge it into the official xdrip build (if it would be accepted)

Ver 0.2.3 (23.02.2020)

  • New. Added option to disable graph on watch
  • New. Added a new watchface without graph (would be used when disabled graph)
  • New. Added option to collect heart rate data from miband. Update interval can be configured in MiFit or any thirdparty application. To see heart rate data in xdrip, the options “Use Health Data” and “Heart Rate sensor” which is located in Settings -> Smartwarch Features -> Smart watch sensors, should be enabled.
  • Improvement. Updated graph watchface view
  • Fixed. Authorisation issue on some miband 4 devices
  • Syncronized with official xdrip version

Added a new options which are available only when enabled engineering mode https://github.com/NightscoutFoundation/xDrip/wiki/Engineering-Mode

  • New. Added option which allow to disable hight MTU (when enabled, can fix watchface sync issues which may happen on some phones, but the watchface uploading would take much more time)
  • New. Added possibility to install custom watchface. The custom watchface files ‘my_watchface.bin’ and ‘my_image.png’ should be placed into into ‘xdrip’ folder on your phone. “my_watchface.bin” is a normal watchface and my_image.png is a watchface background image. The background image shouldn’t have more than 128 colors. For faster delivery and longer battery life, the wathcface size should be as small as possible.
  • New. Added offset option for custom watchface (defines offset between top of the background image and xdrip generated data)

Ver 0.2.2 (09.02.2020)

  • Improvement. Added BG update interval in night mode.
  • Improvement. UI improvements on the band settings screen.
  • Syncronized with official xdrip version

Ver 0.2.1.1 (03.02.2020)

  • Watchface. Fixed HR value when no data available.
  • Watchface. Increased font size for delta and bg date.
  • Fix in watchface generation algorithm which should fix “black” watchfaces reported by some users.
  • Fix. Requesting higher MTU size and use the size negotiated by Bluetooth protocol. (should fix watchface synchronization issue).
  • Improvement. BG alarms now work as call. On MiBand 3 and 4 the ignore button will delay alarm, and hangup will snooze alert.
  • Improvement. Authentification for miband2 and 3 (no need to approve auth after disconnection).
  • Improvement. Decrease brightness when uploading watchface. This can significantly improve band battery life. Also makes watchface update to be not so noticeable to people around.
  • Improvement. Added night mode settings.
  • Resend BG as notification if watchface cannot be installed when the battery level is less than 10%

Ver 0.2.0.1 (29.01.2020)

  • Quick-fix to fix a empty watchscreen and small styling issues

Ver 0.2.0 (29.01.2020)

  • New algorithm to represent glucose data, which use a dynamic watchface with a custom background. This allows using all miband features. (only for MiBand4)
  • Like in previous versions, MiBand 2 and 3 can receive bg values as a notifications.

347 thoughts on “Future of the xdrip miband project

    1. Cannot get this working with new band 5 on Samsung M51. Used latest modded Mi fit app (firmware updates) have latest version of xDrip+ followed all instructions to the letter (got freemyband txt file with mac code) When I uninstall modded Mi app and reinstall official Mi app firmware updates again. xDrip simply will not find the band so is useless for what I wanted from it. Very disappointed

      Like

      1. Hi. First of all, i want to make sure you use the latest modified xdrip from my blog (not the official version) . If everything ok here, then I want to clarify, do you receive a bg value on your band if you leave the modded mi app?

        Like

  1. Hi, great work! Can the mod xdrip version be installed on Android 5? I will try it in another phone, but my daughter’s one has Android 5 and I’m not able to install on it so far. Thanks a lot

    Like

    1. I finally can instal the new xdrip version, and I can manage to connect xdrip to the mi band 4. but it seems xdrip is not sending the watchface. if I send the notifications as text it works.
      If I try to send them as watchface, the band says syncronising, and then it send an error (syncronising error).

      Like

      1. If I am not mistaken, the minimum android version for the official xdrip is android 6.0? Can you check if you can install official xdrip apk? Regarding watchface problem, it can be related to some specific FW version installed on your band. Can you go to System Status -> Miband page and share a screenshot from this view? Thanks.

        Like

        1. Hi, sorry, i dont know how tu post a picture here. The firmaware version of miband is V1.0.9.22

          this is what i see on the miband page

          Model: Mi Smart Band 4
          Software version : V1.0.9.22
          Mac address: E4:Ba:73:31:70:DA
          Connected: Yes
          Is authemticated : Yes
          Battery: 92%
          State: Sleeping

          Thanks a lot!

          Like

  2. I think I didn´t mention it but I have installed the last version of yoru xdrip Ver 0.2.0.1 (29.01.2020).
    Regarding the instalation issue, I have to install an app for manage the apks. It didnt happend this with the original version (I was ussing v20190924), but that seems to solve the problem.

    Like

  3. Hi, as I see the miband4 ver. 1.0.7.60 with the latest xdrip 0.2.0.1 worked fine, but after actualization the miband4 to ver. 1.0.9.22 there is a problem with syncronisation to xdrip. We have decided to use the older ver of xdrip 0.1.4. But still – great job 🙂

    Like

  4. Nice approach, indeed.
    Nevertheless I decided to stay with 0.1.4 and wait for updates of that – 0.2 has the habit of switching the screen on every 5 minutes, and even if it’s only for a few seconds, it’s distracting.
    Even worse, this behaviour attracts attention of other people, and I don’t want to explain what’s going on there, and why I need to get told about my blood glucose level.

    If a way can be found to update the display silently, I’ll return.

    Thanks nevertheless for this awesome development!

    Like

  5. During installation, the progress bar does not come to an end and I get the message “the application has not been installed” what could be the reason?

    Like

      1. Please try the following solution. Open “Play Store” application => tap on Menu button => select “Play Protect” option => Disable the options “Scan device for security threats”.

        Like

    1. Please try the following solution. Open “Play Store” application => tap on Menu button => select “Play Protect” option => Disable the options “Scan device for security threats”.

      Like

      1. Thanks, i tried this but i still get an error message that the app can not be opened/installed.

        I am on Android 9, Sony Xperia XZ1 compact.

        Like

        1. Ok, i found a solution for this.

          Deinstall any existing version of the ‘xDrip’ app first!
          Install the patched version of the ‘Mi Fit’ app AND the modded version of the ‘xDrip’ app from your SD card.
          Everything should work now.

          Hope that helps.

          Like

          1. Oh yeah, you are correct. Sorry i didn’t read this. I also wanted to thank you for your work. I am using your Mi Band patch for the last few days, and my blood glucose has been exceptionally good now that i can receive all the alarms my watch and act accordingly.
            Thanks a lot! 🙂

            Like

  6. Hi,

    i installed your latest APK but i dont get the right MiBand Config screen. Looks to me like the original configuration screen. I dont have any options for the authkey for example.

    What can i do?

    Regards
    Volker

    Like

    1. Most possibly the xdrip cannot find your watch. Please go to miband setting in xdrip and try to enter the band mac address manually (the mac address can be found directly in the band menu or in mifit settings). After this, exit to the main xdrip menu, and go back to miband menu. Now you should see the auth filed, which normally should be populated with the correct key which was automatically extracted from the patched mifit application.

      Like

        1. Unfortunately, no. This watchface was optimized as much as possible to achieve a very small file size (for faster delivery) and it has dynamically generated background so there no way to move elements on the background.
          I also planning to add another watchface, with big time digits and without a graph, like it was on v0.1 . If you have some suggestion regarding design, let me know.

          Like

          1. Works! Thank you! my daugther like so much

            Will it be possible to design own (not Watchfaces) backround image maybe pink (this is just black) or my daugther like unicorns 🙂

            Like

  7. Many thanks for sharing your hard work with us.
    Unfortunately, as some of other people, I am unable to install Xdrip miband4 integration app.
    What might be the reason other than Play Protect?

    Like

    1. It can be you have original xdrip application version installed on your phone. Please go to settings/apps and try to search for xdrip. If you find xdrip application here. you need to delete it. Also, try to open installation apk file via file browser(not chrome).

      Like

    1. Is it necessary to unpair the Mi Band from the Mi Fit application and set factory reset first? How to do it if I want to return Mi Band to the factory setting?

      Like

      1. If you really need to return your miband to factory settings, you can install patched mifit and perform a factory reset. After this follow all steps from “Obtaining auth key” chapter.

        Like

    2. Yes, you need to just delete an old xdrip, and install a new version. I also suggest to save xdrip setting and restore these settings in the new xdrip, so you would not need to reconfigure it again.

      Like

    1. This already in my TODO list 😉 but need to investigate miband command protocol a little more. I’ll try to do this after i finish basic functions related to glucose.

      Like

  8. Hello
    you did a great job and as soon as i saw it i immediately bought the MI Band 4 to try it.
    I think the version 0.1 is fantastic for its easy way to use for children and my wife, even if we lose some functions that are still easily visible on the phone.
    I made little changes to the watch face to control the battery charge and enlarged the bluetooth symbol to see it better.
    The problem is that I can’t understand how to change the watch face with the modified one.
    I send the watch face to this e-mail to share it: bigdigital.kov@gmail.com
    Thank you
    Michele

    Like

  9. Hi i did everything from the list and i get the notifications. But when i turn it off to recive the watchface, my band show the green icon “Synchronization” and then a red one with information “synchonization unsuccessful”. Wht’s wrong? I’ve downloaded version 2.0 and 2.0. Thank you for any feedback.

    Like

  10. I’ve tried version 2.0, 2.0.1 and 2.1.1. Version 2.1.1 send only notifications and I dont see where turn it off to get watchface.

    Like

  11. bigdigital it’s really great work. After all, it works for me equally. The problem was that I didn’t uninstall the previous version of xdrip before installing xdrip miband.

    Like

  12. *** Awesome ***
    Thanks a lot: Had to uninstall my current xdrip to get the patched xdrip installed, also I had to enter the Mac Address and the Auth Key manually. Since that, it works like a charm! :-))
    As my beloved pebble may soon be gone – after 3,5 yrs, I’m glad to have this little mi band ready with your patch.
    Thanks again

    Like

  13. Hello, I have 0.2.0.1 version and the miband4 ver. 1.0.9.22 and there is a problem with syncronisation to xdrip. My band show the green icon synchronization and then a red one with information about no synchronization.

    Like

  14. It’s working perfectly fine! I have no words to describe how glad I’m to use your watchface. Congratulations.

    Like

  15. Hi, first of all thanks for your work, it’s working perfectly fine and is helping so many of us!

    I am also developing apps privately and did a lot of UI designing and would love to try some things with the watchface design. Is it possible to share your code?

    Thanks a lot!

    Like

  16. Hi bigdigital,
    great idea and implementation path. I try to get your xdrip 0.2.2 working. But the I pair my miband4 it always comes back with some error message: “MiBand authentication failed due to authentication timeout. When you Mi Band vibrates and blinks, tap it a few times in a row.” Unfortunately tapping doesn’t help. (I can see the automatically retrieved correct Mac address and Auth Key values in xdrip.I am running this on an Xperia XA2 with Android 9.
    Do you have any idea, what else I could try?
    Thank you,
    Martin

    Like

    1. Hi. This error means that something wrong with auth key you use. Can be it was changed . I suggest you regenerate it. For this, reset you Mi Band and follow all steps from ” 1. Obtaining auth key” procedure.

      Like

      1. Thank you for your fast reply.
        I tried to reset the Mi Band about 6 times now. I tried to unpair the Mi Band before uninstalling the Mi Fit mod apk or to leave it paired, when uninstalling. Both times the result is the same.
        The only oddity I could see is, that the keyfile is NOT saved to /sdcard/freemyband on my phone, but to /internal_storage/freemyband/. In order to get it auto-read by xdrip+ 0.2.2, I copied it manually to /sdcard/freemyband/. Do you have any further ideas, what’s going wrong here? (btw. I work in IT and development, so I would hope, I am able to follow those instructions correctly 😉 )

        Like

        1. Ok. to understand why this happen i would need an error log. For this please go xdrip Settings->Less common settings-> Extra logging -> Extra tags for loggings and enter here “MibandService:d” (without quotes) . After this go to “Less common settings” -> View recent error interface . Leave enabled only “Low” checkbox . Search “Requesting to enable notifications for auth” message and make a print screens till to the error “MiBand authentication failed..,” . You can send screenshots to my email bigdigital.kov@gmail.com

          Like

  17. Hello,

    You have made a great job. Thank you for your work.

    Is there any option to edit your skin and create our personal watchfaces?
    What program have you use to create the skin? How have you installed the skin in the band?

    In my personal case, I don’t need to see the graph in the band or the four color line at bottom.

    I prefer to have a bigger clock numbers and glucose number change the color if value is low or high.

    Thank you again for your work.

    Like

    1. Hi, unfortunately, there is no way to create custom watchface. The watchface has a strict structure and color palette. And the half of the watchface generated on the fly in the xdrip. But i almost finished a new xdrip update where you can disable graph and istead of the graph, there would be a big clock. The glucose hight / low number color has the same color as you have set in xdrip settings for hight / low graph lines

      Like

      1. Hello,

        I’ve been customizing watchface.bin file located in path /SDCard/xdrip/. I have used WF_builder program.

        I have changed 000.png image deleting the graph (then, in Xdrip, I will chang “graph time” to 0 hours), translated weekdays to my languaje, changing format date (day / month) and finally I have enlarged hour numbers (you can check my design in the next URL https://imgur.com/e5m6rnZ )

        I have exported the design as watchface_pallete.bin and watchface_raw.bin, I have tried to rename bin files and copy then to /SDCard/xdrip/watchface.bin. But I weren’t able to make it works.

        Is there any way to use my design in your xdrip 0.2.2 release?
        Could you prepare next xdrip release to add customs watchfaces easily, for example, modifying ?

        How do you create your own version of xdrip?

        Thank you very much

        PD: Do you know if it is possible to uninstall and install your new Xdrip release without loss old readings?

        Like

  18. Hi there,

    first off all i want to say big thanks for your work. I hope i get my band working soon. Have the same problem like martin.

    “MiBand authentication failed due to authentication timeout. When you Mi Band vibrates and blinks, tap it a few times in a row.”

    My Band recieves messages every 5min. It asks if i want to connect. After typing yes it says connectet. Then after some seconds xdrip shows message above (authentication timeout). Seems like the communication is not working from mi band 4 to S8.

    Using Samsung S8, Android 9, xdrip 0.2.2.apk

    Is there a solution?
    Big thanks again.

    Like

      1. Hey, thanks for the fast reply.
        For me it somehow doesnt work. Tried everything.
        Generating auth key is no problem. Xdrip finds band autimaticly. Manually typing/ copying mac address/ auth key doesent help. Always getting timeout massage.

        Error log like described above ( February 14, 2020 at 9:29 am) under following link.

        Is it necessary to uninstall patched mifit app after generating auth key?

        Do i have to install normal mifit app for use with xdrip?

        Thanks for your help.

        Like

        1. I see you have 108308 error code. This code means miband do not accept auth key. So seems you did something wrong on “Obtaining auth key” phase. Maybe try to reset your miband, delete /sdcard/freemyband folder and retry all steps from the beginning and DO NOT unpair miband when you get auth code.

          Like

          1. Made several factory resets. Always getting same “timeout” Message.
            At least generated auth key on different mobile with resettet band. Typed in the address and key manually on my phone with xdrip. Same issue.

            Any further ideas?
            thanks in advance for your patience.

            Like

                1. Hi Artem,
                  yes, I am aware of xdrip not needing any 0x in front of the auth key. Also obvious, because as far as I remember, the auth key field in xdrip is limited in characters, so an additional 0x would cut off the last 2 digits/characters of the key.
                  I had reset the MiBand4 and started the process: Installed the MiFit mod app, paired the miband, made sure the app had written the auth-key-file, removed the mifit mod app from the running apps, forced the app to stop (no deinstall), removed the band from the systems known bluetooth devices, called gadgetbridge, added the band (with using the key from the written file, prepended by 0x).
                  Then I unpaired the miband from gadgetbridge, stoppt the app (killing forced), unpaired miband in the system. I switched to xdrip (always active, as I am looping), tried adding the miband, but got the same 108308 error with doing so.
                  So I thought, maybe this only works on the first thirdparty app, so I reset the band once again, added it to mitfit mod app as before, killed the mifit mod app, removed miband from the known bluetooth devices from the system, went into xdrip and tried to add the miband there. but again I get the 108308 error (with the current MAC and auth key of course).
                  Regards,
                  Martin

                  Like

                    1. Hi Artem,
                      thank you for releasing your xdrip+ 0.2.3. I tried out this new version as suggested, and I could authenticate the MiBand 4 successfully this time. Now I can focus on the minor settings 😉
                      Thank you,
                      Martin

                      Like

  19. Hello,
    At first, grest job. Only one comment and one question.
    I think that is better to show the number of minutes from last reading, like Nightscout, than last time.

    Why some people cant install the watchface, they tellme that the band is linked with modified xDrip but the watchface doesn’t install.

    Thanks!

    Like

    1. I’m afraid this is not possible to do. The wachface is static and to display a number of minutes from last reading it would require to syncronize watchface every minute. Such approach will significantly decrease battery life, in addition, if band will lose connection with the phone, this value would not be updated and you would think that this is a fresh data. So the only possible way to display last reading time is to use a current approach.

      If you mean that issue when miband cannot synchronize watchface. Still not sure. Seems this is somehow related to the android build. There was an update that seems works for most of the people, but there are still some people that have synchronization issue. So at least make sure the people use the latest xdrip version available here

      Like

      1. Hi.
        I decided to write a comment because I think already the third day.
        I will add that I have already set up one mi4 team and it works beautifully. Our bands differed in that mine was used so far, and a friend took a new one from the packaging. Works great! Thanks for your instructions I did according to them.

        Unfortunately my team can’t do it. I do everything the same.
        Earlier she was connected to her daughter’s phone. However, I removed the steam and entered the factory settings. And then I set up my phone in the same way as my friends.

        On the band, when a new sugar reading appears in xdrip, does it vibrate and show if it ‘evaporates’ now?
        And every time this way. I click ok and nothing happens. A message pops up saying that I should push the screen. I press and nothing.

        I have no idea, it’s frustrating. : (((((
        Can I count on help?
        My email is ravtenna@gmail.com

        My Phone is Huawei mate 20 lite.

        Like

  20. Minor nitpick: Upgrade from 0.1.4 to 0.2.2 removed auth key entered before (there’s no file containing the key because unlocking was done somewhere else).

    Like

  21. hello, my problem is that after the first correct installation of mifit mod, obtaining the key and correct installation of xdrip-miband ver 0.2.2 I had problems with synchronization, so I reset miband4, uninstalled both modes, deleted the freemyband directory and returned to the original xdrip. Now, when reinstalling mifit mod, it no longer creates this directory, after transferring the installation file to another phon it also does not create it. I have no way to get this data to install your latest version. Please help fix what I have unwittingly broken

    Like

  22. Bonjour, merci d’abord pour vos efforts, j’aurai aimé que les chiffres de la glycémie soient une peu plus grands notamment dans la version qui n’affiche pas de graphe,.par ailleurs xrip+ n’affiche plus le nombre de pas ni la fréquence cardiaque, comment puis-je réparer cela?

    Liked by 1 person

    1. This is an optimal text size to fit 3 possible blood sugar digits on the screen. But i’ll check if it is possible to increase it a little bit. Regarding heart rate, yes it was removed from th main screen, there was to much information on the screen, in addition, you can see the heart rate in the miband menu. The step numbers should be at the bottom of the screen (near to the battery)

      Liked by 1 person

  23. Hello, thank you first for your efforts, I would have liked the blood sugar figures to be a little larger especially in the version which does not display a graph,. Moreover xrip + no longer displays the number of steps nor heart rate, how can i fix this?

    Like

    1. Hm, it looks fine on my band. Does the bg digits have the same outline if you use watcface with graph?
      (actually they use the same functions to draw the text and this function wasn’t changed in v0.2.3)

      Like

    2. Hello Stephan,

      I had the same issue using watchface without graph.
      I didn’t touch anything and BG numbers font was correct in the next update.

      Rigth now I have changed watchface design and I had the same problem with BG value.
      When BG value has updated, it looks great. In the next pictures you can see before ( https://imgur.com/tWCO3Ui ) and after ( https://imgur.com/IU11Vg6 ).

      Bigdigital, any idea why the first time BG is difficult to read and later is works OK?

      Thank you very much for this version (v0.2.3), It is better that last one.

      What will you update in next release?

      Like

  24. in this version I can’t see on XDRIP neither heart rate nor number of steps, I’m talking about the display on this version of XDRIP, how I can fix this.Thanks a lot

    Like

  25. The last version 0.2.3 works just perfect with Miband 4 ver. 1.0.9.30! Great job!
    Thank you so much.
    Probably, it would be possible to add more information to display: the bolus or/and basal. In this case it will be fit perfect for using with OpenAps.

    Like

  26. Hi. tank you for your work!
    I have a problem: I can not send the watchface to my band 4.
    I set “allow to use custom watchface” but noyhing happens.
    I’m using the last release. Band is connected with xdrip and can get BG as notification.
    What am I missing.
    My smartphone is Xiaomi mi9 running Android 10

    thank you

    Like

  27. I guess it’s a question that someone will know from here.
    can we use huawei gt or gt2 with a similar method ??

    Like

  28. 0.2.4 – can see the trend line (can it be disabled somehow?) but there are no boluses marked – which color should I expect?

    Like

    1. Hi, you would see the bolus like only if enable show bolus option in the miband menu settings. The boluses would be displayed with the same color as in xdrip apk.

      Like

  29. ciao ho seguito il link e sono riuscita a sincronizzare mi band 4 con samsung s8 uso dexcom g6 ma il quadrante del mi band non aggiorna glicemia in cerca di consigli mando foto grazie

    Like

  30. I tried the 0.2.4 version on two Smartphones, Android 9 and 10.
    The xdrip App Crash at the settings.
    Version 0.2.3 is OK for both Smartphones.

    Like

      1. Had the same problem here.
        Meanwhile everything is working fine.
        My solution: installing 0.2.3, making every settings here and then updating to 0.2.4

        Like

  31. I cant find aut code, because the mi fit mod doesn t run well: i cant access…
    Android 9
    Note 8
    And A40
    Happens the same

    Like

  32. Wen I update to V0.2.4.1 the miband stop synchronize data from tho phone. Wachface show the last synchronize data. When I return to V0.2.3 work fine

    Like

  33. Hi! At first I’d like to say big “THANKS” for your work.

    I have a problem with “show bolus” option. Graph is enabled, show bolus too but bolus is not displayed on miband 4. Help, please.

    Like

  34. Had a problem with syncronization too. Opened MiFit, Miband updated its firmware. Doesn’t help. Even “Update BG manually” didn’t work. Checked settings and founded that there was “Allow to use custom watchface” enabled. Turned it off and everything works again.
    Thanks for really usefull mod, great job! Thanks again!

    Like

  35. Great work. Love the Miband option. Thank you! Was it difficult to add the Miband option to Xdrip? The reason Im asking is I use the Bubble device on my Libre14 and its connected to Diabox. Then Xdrip picks up the information via Internal HTTP on the phone through Diabox. I just got the Ticwatch pro and want to use it as a collector when the phone is out of range with out using Diabox. This would require the Bubble version of Xdrip which does not have the Miaband option. I use the Miband at night when I sleep to get notifications that vibrate so I dont wake the wife.

    Like

    1. One thing I noticed is that the date format is not for my country. Not a big deal for me but can it be changed in xdrip or do I need to make my own watchface for this?

      Like

    2. @Freddy, you didn’t bolus, did you? (With 195 mg/dl, I’d become nervous.) If you did: there’s no indication of that on the Mi4 screen…

      Like

    1. OK, I have deinstalled mifit ( don’t need it), but I only found the “show date on the screen” setting in miband settings nothing for the date format?

      It worked good the last hours but now I got a problem with the Synchronisation. The “update manually” button works but not the automatic sync, I enabled MTU option but still no auto sync.

      Will look into this tomorrow, it’s late in My country 🙂

      THX for the fast reply 🙂

      Like

  36. Hi, I’m really sorry to ask this but I just don’t get it – I updated the latest xdrip version and can get notifications to my Miband, but where do I download the dynamic watchface with the graph? Or what settings do I need to change so I get the watchface sent, not just notifications?
    Thank you so much 😀

    Like

    1. Hi,
      in xdrip in the settings for the Miband is an option called “BG readings as notification”. This must turn off to get the watchface on the Miband, otherwise you get only notification.
      This was my fault too at the beginnig 🙈

      Liked by 1 person

      1. thank you, but if I do that, nothing happens, I don’t get anything sent to my Miband.
        I couldn’t find the my_watchface file either to move them into the xdrip folder – where do I get them from?

        Like

  37. Where does the my_watchface file come from?
    Do I need to delete and reinstall xdrip or delete and reinstall miband?
    I still haven’t found those files 😦

    Like

      1. I thought I needed to put this file into the xdrip folder so I would get the dynamic watchface sent instead of a notification?
        Currently I have it set to Send BG as Notification and it works fine, but if I keep Send BG but turn off As Notification, nothing happens and I don’t get anything sent to my Miband.

        I’m not quite sure I understand what I need to do to get the updated notification with the graph and everything to my Miband.

        Thank you for helping me.

        Like

        1. The watchface will be sent each time the display gets updated, there’s nothing you must do.
          But – as I reported below – I had to install 0.2.2, 0.2.3 and 0.2.4.1 in this order to get the graph working. You should try this first. (If you cannot get the band paired/authenticated, go and restart the phone.)

          Like

          1. Thank you Steve, I still can’t get it to work.
            I downloaded 0.2.2, 0.2.3 and then 0.2.4.1 and managed to pair and authenticate the Miband but nothing is being sent. No watchface if I leave BG Readings as Notification unchecked.
            Did you have to pair and authenticate the Miband after each xdrip version?
            ie. install 0.2.2 – pair with miband, check sensor and transmitter is working,
            install 0.2.3 , same
            then 0.2.4.1?
            I have a Samsung S7 if that somehow matters.
            I factory reset the band and used the FreeMyBand miband app for a new authorization code and that all seems to work – just no graph or watchface –
            However if I change it in settings, BG as normal notification to Miband works again now.

            Any other settings I need to check or can try out?

            Like

          2. I think I may just be too dense for this, I lost a bunch of data, but my sensor is jumping around today anyway and now I’m back at the same point I started at – just notifications, no watchface. Very odd.

            Like

  38. Finally, I got 0.2.4.1 working, but only after installing 0.2.2 and 0.2.3 first, and after a few restarts of both the band and the phone to get the band authorized.
    Even bolus marks do show now.
    So far so good – but since we have switched to daylight savings time a few days ago, how would the band learn about the new time zone? I had to disconnect it from xDrip, add it to GadgetBridge and run the setup there – with the first update of the settings (e.g. the selection of features) also the time was set to the correct zone. Will I have to repeat that twice per year? (What if the band’s clock drifts? Will it get re-synced, by xDrip only?)
    I hope the MiBand code will be merged into the xDrip master soon – there have been updates of xDrip since 0.2.4.1 was released, and there are more to come.

    Like

Leave a reply to GXG Cancel reply

Design a site like this with WordPress.com
Get started