Closed Thomas-Wolff closed 2 years ago
Now already with the third eros Pod problems with the Pod change to AAPS 2.8.2.7-dev Bulid 04a104a9b.
1st Pod deactivation started and confirmed accordingly, then screen froze again until the field message 'Close APP' or 'Wait' came up. Confirmed with wait Pod worked audibly and deactivated. Then the error message 'Data coming from another pump' appeared again in the main tab. Change the pump driver. I simply confirmed this and then proceeded to activate the new eros Pod.
Despite these problems, Pod was initialised cleanly and so far runs cleanly in AAPS-dev.
@MilosKozak I still see a considerable need for action to fix these errors.
My hardware Samsung Galaxy A40 Android 11. Attached are a few screenshots and the corresponding log file for documentation.
Many greetings Thomas
Hi @Thomas-Wolff
@MilosKozak is managing the entire development of AAPS, so he may not have much time to give feedback on this issue. I'm happy to do so, since I authored the latest integration.
There is a general issue with Eros, where long running interactions (e.g. with the pump) freeze the user interface. I expect this to happen in most places where you are waiting, and do plan to fix this asap. Unfortunately, I do not have many evenings or weekends available to me currently, so fixes for this are slow to happen.
I am also reaching out to other developers that may assist in the meantime, and hope we can get if fixed soon. In the meantime, thanks for sending these reports, they are helpful!
@Samspycher thank you for your feedback.
No problem, please have a look at this, despite these errors I have always been able to get my eros pods to work.
Have a nice weekend Greetings Thomas
Hi, had the same problem with the freeze and data coming from different pumps message. Latest dev (258224055). Logs attached.
I'm not sure if it helps but for me, the exact freeze was after the "stick to your body" window closed and before the ritating wait blue circle appeared. I never saw the rotating circle.
I have the same on dev 95f6cc7a:
2021-11-09 19:13:28.071 993-993/? D/CompositionEngine: writeOutputDependentGeometryStateToHWC layer[info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity#0] set Z 134217728 miFodLayer 134217728
2021-11-09 19:13:28.088 993-993/? D/CompositionEngine: writeOutputDependentGeometryStateToHWC layer[info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity#0] set Z 134217728 miFodLayer 134217728
2021-11-09 19:13:28.103 993-993/? D/CompositionEngine: writeOutputDependentGeometryStateToHWC layer[info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity#0] set Z 134217728 miFodLayer 134217728
2021-11-09 19:13:35.928 1810-2321/? W/InputDispatcher: reportMqsWindowUnResponse windowName:39e5fc6 info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity (server)
2021-11-09 19:13:35.928 1810-2321/? E/system_server: report event v2: module is BSP-Touch , appId is mqs_bsp_touch_data_4731000 .
info is {"fod_single":0,"fod_unlock":0,"double_wakeup":0,"touch_click":0,"ghost_touch":{"double_down_position":"0","double_down_position_charging":"0","times_of_same_position":"0","times_of_same_position_charging":"0","double_down_axis":"0","double_down_axis_charging":"0","long_press":"0","long_press_charging":"0","multi_point":"0","multi_point_charging":"0","lcd_noresponse":"39e5fc6 info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity (server):1"} } .
2021-11-09 19:13:35.929 1810-2321/? I/WindowManager: Input event dispatching timed out sending to info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity. Reason: 39e5fc6 info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity (server) is not responding. Waited 8008ms for FocusEvent(hasFocus=true)
2021-11-09 19:13:35.957 1810-2321/? W/InputDispatcher: Canceling events for 39e5fc6 info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity (server) because it is unresponsive
2021-11-09 19:13:37.083 6182-6262/? D/EVENTS: [OmnipodErosPumpPlugin]: [RxBus.send():23]: Sending EventNewNotification[notification=info.nightscout.androidaps.plugins.general.overview.notifications.Notification@e55b72]
2021-11-09 19:13:40.058 1810-24602/? E/ActivityManager: ANR in info.nightscout.androidaps (info.nightscout.androidaps/.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity)
PID: 6182
Reason: Input dispatching timed out (info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity, 39e5fc6 info.nightscout.androidaps/info.nightscout.androidaps.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity (server) is not responding. Waited 8008ms for FocusEvent(hasFocus=true))
Parent: info.nightscout.androidaps/.plugins.pump.omnipod.eros.ui.wizard.activation.ErosPodActivationWizardActivity
Load: 0.0 / 0.0 / 0.0
----- Output from /proc/pressure/memory -----
some avg10=0.01 avg60=0.42 avg300=0.24 total=496508844
full avg10=0.00 avg60=0.03 avg300=0.01 total=140998111
----- End output from /proc/pressure/memory -----
CPU usage from 34284ms to 0ms ago (2021-11-09 19:13:01.673 to 2021-11-09 19:13:35.957):
Maybe "Waited 8008ms for FocusEvent(hasFocus=true))" is too short and we can set a timeout higher?`
complete log: aaps-dev-set-new-pod-hanging.txt
Can confirm the issue persists with 3.0beta5, and only on activating, not deactivating.
Good morning to all. Just changed my eros pod, everything went through fine, no more frozen screens. The only other thing I noticed was the message 'Data coming from another pump ........' but not as a remote message on the AAPS main screen but only on the main screen of my phone as a notification.
@MilosKozak if you could take another look at this, that would be wonderful.
AAPS 2.8.2.10-dev Build: 54b8d0613
Have a nice Sunday Greetings Thomas (Bearbeitet)
Enclosed is the corresponding log file:
on my side, the frozen Problem is fixed.
Will try when the next 3.0beta is branched. Hopefully today or tomorrow since beta5 expires on Wednesday.
referring to problem #775.
Screen is still frozen and after a short time the error message 'Close APP' or 'Wait' appears, both times with Wait confirmation, after which the activation continued.
On the positive side, the POD was nevertheless activated cleanly and APPS 2.8.2.7-dev immediately started working.
Due to this activating behaviour, I still see a certain need for action.
With best thanks in advance Thomas