Task deadlock on: runWixelReader! log?

[bordeb]

Hi! Latest stable version of xdrip (on Samsung Galaxy A8 (2018), Android 9) with several LibreAllHouse RPis arround the house, after changing from Libre1 to Libre2 sensor (EU sensor, direct BT connection to the sensor without MM, using OOP2 latest), on the xdrip screen I am noticing the log:
jamorham Home
XX:XX Home toast message next: xx:xx Task deadlock on: runWixelReader! @XX

I think that it is related with LibreAllHouse connections and I am wondering why it is displayed? Is this maybe related with "Inter-app settings" > xDrip Web Service: enabled & Open Web Service: enabled, which is required for Libre2 with LibreAllHouse?

EDIT: forget to mention that everything works ok. Only this log is sometimes displayed and can not figure it out why nor if/how to disable it?

[Navid200]

@tzachi-dar

[bordeb]

Thank you very much @Navid200 for mentioning @tzachi-dar ! :-) I am fully aware that he is the guru for the answers in this field, but nevertheless, I did not want to address him directly here, as I did not want to be pushy. I was just hoping that someone more knowledgeable than me will help here! Thank you very much!! I really appreciate your time and time from other experts here in this community!

[bordeb]

After 1,5 years (with latest stable release ), I am still noticing this notification on the screen. Are there any new insights why this is happening and can this be resolved? Tnx in advance!

[bordeb]

1.) The last time the xdrip was installed was approximately a month ago on a new phone, clean install of the latest stable version and then imported saved setting from the old phone.

2.) Tomato is for MiaoMiao, am I right? Do you ask me if I made clean xdrip install when I was switching from MiaoMiao to direct Libre2 using OOP2? The swithc from MM (Libre1) to Libre 2 with OOP2 was approximately 2 years ago and in that time I did not uninstalled xdrip, only changed settings and installed oop2.

[Navid200]

If you have time, an experiment can help.
You should first do a database backup, which saves both the database as well as the settings: https://navid200.github.io/xDrip/docs/Backup-Database.html

Then, uninstall xDrip. Now, do a fresh install. But, don't restore the database or the settings.
Then, set up xDrip.
Do you still see the log?

[bordeb]

Uhh, :-) I see.
I will try but it is a master for my kid and it will be a real effort to synchronise us all, so am not sure when it will be possible because of school etc..

Instead of uninstall/install, is it the same to just reset the xdrip app through cleaning storage and cache in the app settings?

[bordeb]

@bordeb When was the last time that xDrip was installed? When you switched from Tomato to OOP 2, you did not uninstall, did you?

When you say Tomato, you mean the Tomato app for MM? I think I confused xdrip data source withe the app Tomato. We have never used the Tomato app, always the xdrip. Does it make any changes?

[Navid200]

It may be. But, it is better to uninstall as long as you create a legacy backup.
After you restore, you will be back to exactly what you had before. In other words, you can undo the experiment by restoring the backup.

This shouldn't be necessary.
The problem is that I am not a Libre user. It will take me a long time to understand everything that is going on with respect to Libre.
I don't have any personal experience with this part of the code.

Another approach would be to disable the master phone temporarily and replace it with a test phone with a fresh install and not restoring anything from the original phone on it. Do the logs show up on the test phone?

Considering I have no experience with Libre, I am not even sure if you can do this experiment with an existing sensor or if you have to do it when you start a new sensor.

Alternatively, we have to leave this and hope that someone else with more experience will help.

[Navid200]

@PhilTU
Have you ever seen either the following toast or log?

Task deadlock on: runWixelReader!

[PhilTU]

I do not recall seeing it. I don't use the all house thing.

[bordeb]

Uhh, :-) I see. I will try but it is a master for my kid and it will be a real effort to synchronise us all, so am not sure when it will be possible because of school etc.. Instead of uninstall/install, is it the same to just reset the xdrip app through cleaning storage and cache in the app settings?

…

On Sun, 19 Jan 2025, 23:26 Navid, ***@***.***> wrote: If you have time, an experiment can help. You should first do a database backup, which saves both the database as well as the settings: https://navid200.github.io/xDrip/docs/Backup-Database.html Then, uninstall xDrip. Now, do a fresh install. But, don't restore the database or the settings. Then, set up xDrip. Do you still see the log? — Reply to this email directly, view it on GitHub <#2871 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF33ROPWN3F3GEEUOAFN6FL2LQRALAVCNFSM6AAAAABVKNNMK6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBYGQ2DKOA> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[PhilTU]

xDrip can take over a Libre sensor any time in its life. Also can reconnect. Necessary as can't start the sensor from xDrip

…

On Sun, 19 Jan 2025, 23:07 Navid, ***@***.***> wrote: It may be. But, it is better to uninstall as long as you create a legacy backup. After you restore, you will be back to exactly what you had before. In other words, you can undo the experiment by restoring the backup. This shouldn't be necessary. The problem is that I am not a Libre user. It will take me a long time to understand everything that is going on with respect to Libre. I don't have any personal experience with this part of the code. Another approach would be to disable the master phone temporarily and replace it with a test phone with a fresh install and not restoring anything from the original phone on it. Do the logs show up on the test phone? Considering I have no experience with Libre, I am not even sure if you can do this experiment with an existing sensor or if you have to do it when you start a new sensor. Alternatively, we have to leave this and hope that someone else with more experience will help. — Reply to this email directly, view it on GitHub <#2871 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASFVQB55VC6ULXJQAN43AED2LQV23AVCNFSM6AAAAABVKNNMK6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBYGQ3DENA> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>