search

home-assistant / android

:iphone: Home Assistant Companion for Android
https://companion.home-assistant.io/
Apache License 2.0
2.23k stars 623 forks source link

Next Alarm sensor - Allow List selection not working #4513

Open bjarnekrottje opened 1 month ago

bjarnekrottje commented 1 month ago

Home Assistant Android app version(s): 2024.7.1-full

Android version(s): Android 14 (OxygenOS 14.0.0.700 (EX01))

Device model(s): OnePlus Nord CE 3 Lite 5G (CPH2465)

Home Assistant version: Core: 2024.7.2 Supervisor: 2024.06.2 Operating System: 12.4 Frontend: 20240710.0

Last working Home Assistant release (if known): Unknown

Description of problem, include YAML if issue is related to notifications: If I try to open the Allow List selection popup for the 'Next Alarm' sensor to select which apps are allowed to register the alarm notifications, the Home Assistant app appears to crash and not work. This results in me not being able to select the apps, which triggers alarms from apps that shouldn't trigger an alarm in HA.

If I click the Allow List option, I expect a menu to open in which I can select which apps are allowed to set the 'Next Alarm' sensor.

Companion App Logs:

homeassistant_companion_log_6-14-2024_23-9-53.txt

Screenshot or video of problem:

https://github.com/user-attachments/assets/e23294c3-45d2-4831-8bf8-95994e1aef7f

Additional information: If any more information is needed, I would be happy to provide it. Thank you very much in advance!

dshokouhi commented 1 month ago

hmm the logs actually dont contain the traceback of the actual crash, we will need that in order to fix the issue as we should not be crashing there. If you have access to android studio that would be the easiest way to get them from logcat

bjarnekrottje commented 1 month ago

Hi @dshokouhi, Thank you very much for your quick reply. Of course I am happy to provide you the information you might need. I have used adb with logcat to get the logs from my personal Android phone. For anyone looking at how I have done this (or for validation by you), I ran the following command in the same folder as adb: .\adb.exe logcat | Select-String io.homeassistant.companion.android > logcat.txt Note: Select-String has been used instead of grep since I'm running this on a Windows machine.

While the above command was running, I have done the same steps as in the video above and have triggered the crash of the app. These are the logs that resulted from this: logcat.txt

I hope this file does contain the right logs. If not, I would be happy to look further and see what I can do to help out. Thank you very much in advance!

dshokouhi commented 1 month ago

Thanks for the logs. We may need to get logs again, unfortunately when you grep by teh app name some things go missing. Here i can see the start of a ANR but hard to tell exactly where its happening. After finding the error its best to look at the full time stamp to get the whole error

07-15 20:55:33.970  2142 14790 D ActivityManager: TheiaManager sendEvent:io.homeassistant.companion.android ANR happen
07-15 20:55:35.487  2142 14790 E ActivityManager: ANR in io.homeassistant.companion.android 
(io.homeassistant.companion.android/.settings.SettingsActivity)
07-15 20:55:35.487  2142 14790 E ActivityManager: Reason: Input dispatching timed out (5886c87 
io.homeassistant.companion.android/io.homeassistant.companion.android.settings.SettingsActivity (server) is not 
responding. Waited 5000ms for MotionEvent)
07-15 20:55:35.487  2142 14790 E ActivityManager: Parent: io.homeassistant.companion.android/.settings.SettingsActivity
07-15 20:55:35.487  2142 14790 E ActivityManager:   11% 10957/io.homeassistant.companion.android: 7.4% user + 4.2% 
kernel / faults: 43572 minor 141 major
07-15 20:55:35.487  2142 14790 E ActivityManager:   57% 10957/io.homeassistant.companion.android: 23% user + 34% 
kernel / faults: 6104 minor 14 major
bjarnekrottje commented 1 month ago

@dshokouhi, I have changed the way of retrieving the errors to specify the pid. This can be done by using the following adb shell command:

.\adb.exe shell pidof 'io.homeassistant.companion.android'

After which I used that pid to get the correct logs (I hope ;)):

.\adb.exe logcat pid=14801 > logcat_pid.txt

Here are those logs: logcat_pid.txt

I also specified the *:V flag to make sure to get all of the logs, from the verbose level and up. Command:

.\adb.exe logcat *:V pid=14801 > logcat_V_pid.txt

This resulted in the following logs: logcat_V_pid.txt

Hopefully these logs do contain the right information you need. It does look like this delivered some more details than the previous logs. Just let me know if I can try it again for you or you can use something else. Thanks in advance!

dshokouhi commented 1 month ago

thanks was able to get the whole error.

As I am unable to reproduce on my end, anything you can tell us about the device?

logs ``` 07-15 21:10:50.627 2142 18316 E ActivityManager: ANR in io.homeassistant.companion.android (io.homeassistant.companion.android/.settings.SettingsActivity) 07-15 21:10:50.627 2142 18316 E ActivityManager: PID: 14801 07-15 21:10:50.627 2142 18316 E ActivityManager: Reason: Input dispatching timed out (cb17193 io.homeassistant.companion.android/io.homeassistant.companion.android.settings.SettingsActivity (server) is not responding. Waited 5001ms for MotionEvent) 07-15 21:10:50.627 2142 18316 E ActivityManager: Parent: io.homeassistant.companion.android/.settings.SettingsActivity 07-15 21:10:50.627 2142 18316 E ActivityManager: ErrorId: 5a2d6708-3c13-4ff6-94cd-265334cdade8 07-15 21:10:50.627 2142 18316 E ActivityManager: Frozen: false 07-15 21:10:50.627 2142 18316 E ActivityManager: Load: 0.0 / 0.0 / 0.0 07-15 21:10:50.627 2142 18316 E ActivityManager: ----- Output from /proc/pressure/memory ----- 07-15 21:10:50.627 2142 18316 E ActivityManager: some avg10=0.89 avg60=0.54 avg300=0.21 total=930025925 07-15 21:10:50.627 2142 18316 E ActivityManager: full avg10=0.43 avg60=0.21 avg300=0.08 total=301357010 07-15 21:10:50.627 2142 18316 E ActivityManager: ----- End output from /proc/pressure/memory ----- 07-15 21:10:50.627 2142 18316 E ActivityManager: ----- Output from /proc/pressure/cpu ----- 07-15 21:10:50.627 2142 18316 E ActivityManager: some avg10=5.62 avg60=5.93 avg300=2.50 total=11777927094 07-15 21:10:50.627 2142 18316 E ActivityManager: ----- End output from /proc/pressure/cpu ----- 07-15 21:10:50.627 2142 18316 E ActivityManager: ----- Output from /proc/pressure/io ----- 07-15 21:10:50.627 2142 18316 E ActivityManager: some avg10=4.47 avg60=2.00 avg300=1.00 total=3294421977 07-15 21:10:50.627 2142 18316 E ActivityManager: full avg10=3.73 avg60=1.07 avg300=0.53 total=1480054016 07-15 21:10:50.627 2142 18316 E ActivityManager: ----- End output from /proc/pressure/io ----- 07-15 21:10:50.627 2142 18316 E ActivityManager: 07-15 21:10:50.627 2142 18316 E ActivityManager: CPU usage from 286039ms to 0ms ago (2024-07-15 21:06:03.047 to 2024-07-15 21:10:49.086): 07-15 21:10:50.627 2142 18316 E ActivityManager: 41% 11501/com.travis.callrecorder.oneplus: 28% user + 12% kernel / faults: 2245596 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 11% 2142/system_server: 6.3% user + 4.7% kernel / faults: 109446 minor 27 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 9.2% 14801/io.homeassistant.companion.android: 6.3% user + 2.8% kernel / faults: 59628 minor 137 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 5.5% 14893/com.google.android.webview:sandboxed_process0:org.chromium.content.app.SandboxedProcessService0:0: 4.5% user + 1% kernel / faults: 25592 minor 1 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.2% 1402/surfaceflinger: 2% user + 1.1% kernel / faults: 1627 minor 1 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.6% 17098/com.beeper.android: 1.4% user + 1.1% kernel / faults: 29513 minor 3 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.6% 1754/com.zhiliaoapp.musically: 1.4% user + 1.1% kernel / faults: 23204 minor 6 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.4% 352/usbtemp_kthread: 0% user + 2.4% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2% 20175/kworker/u24:14-ipa_pm_activate: 0% user + 2% kernel / faults: 3 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.8% 26058/kworker/u24:9-kgsl-mementry: 0% user + 1.8% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 15% TOTAL: 7.5% user + 5.7% kernel + 0.2% iowait + 1.1% irq + 0.3% softirq 07-15 21:10:50.627 2142 18316 E ActivityManager: CPU usage from 71ms to 1066ms later (2024-07-15 21:10:49.157 to 2024-07-15 21:10:50.153): 07-15 21:10:50.627 2142 18316 E ActivityManager: 117% 2142/system_server: 50% user + 66% kernel / faults: 4937 minor 44 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 43% 2197/Signal Catcher: 25% user + 17% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 27% 18317/AnrAuxiliaryTas: 6.6% user + 21% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 5.5% 3217/ConnectivitySer: 2.2% user + 3.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 4.4% 10429/binder:2142_1D: 3.3% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.3% 6481/binder:2142_16: 2.2% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.2% 3151/android.imms: 1.1% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.2% 4137/HansLocalSocket: 1.1% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.2% 12081/binder:2142_20: 1.1% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.2% 18315/AnrMainProcessD: 0% user + 2.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 2142/system_server: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 2293/system_server: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 2588/OomAdjuster: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 2589/BroadcastQueue: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 2976/binder:2142_4: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3160/StorageManagerS: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3206/NetworkStats: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3209/WifiHandlerThre: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3250/ConnectivityThr: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3293/oSenseHandler: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3307/OplusWifiCPUThr: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3328/OwmBaseUtils: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3335/OplusSlaManager: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3354/HwBinder:2142_5: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 4813/binder:2142_14: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 4975/HansSocketThrea: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 4996/TrafficStatsHan: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 10422/binder:2142_1C: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 18316/AnrConsumer: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 22286/OwmIcmpMonitor: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 28653/OwmDhcpMonitor: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 59% 14801/io.homeassistant.companion.android: 28% user + 30% kernel / faults: 13901 minor 10 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 48% 14801/mpanion.android: 23% user + 25% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 5.1% 14813/FinalizerDaemon: 1.2% user + 3.8% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.5% 14811/HeapTaskDaemon: 2.5% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 29% 185/kswapd0:0: 0% user + 29% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 32% 11501/com.travis.callrecorder.oneplus: 12% user + 20% kernel / faults: 1587 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 23% 11566/pool-24-thread-: 6.2% user + 17% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 7.5% 11509/HeapTaskDaemon: 5% user + 2.5% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 18% 187/kshrink_slabd: 0% user + 18% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 12% 643/logd: 5.1% user + 7.2% kernel / faults: 542 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 2% 664/logd.writer: 1% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2% 18220/logd.reader.per: 1% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 12% 8937/com.rompslomp_react: 9.9% user + 2.4% kernel / faults: 1500 minor 2 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 11% 8950/HeapTaskDaemon: 7.4% user + 3.7% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 8952/FinalizerDaemon: 1.2% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 9175/SentryExecutorS: 1.2% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 4.9% 7342/com.google.android.providers.media.module: 2.4% user + 2.4% kernel / faults: 1055 minor 46 major 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.6% 7347/Signal Catcher: 2.4% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 5.2% 16616/kworker/X26:6-kverityd: 0% user + 5.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.9% 16657/adbd: 0% user + 3.9% kernel / faults: 6 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.6% 5938/UsbFfs-worker: 0% user + 2.6% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 16657/adbd: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 18219/shell svc 18218: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2% 12/rcu_preempt: 0% user + 2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2% 30/rcuop/2: 0% user + 2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2% 484/com.google.android.apps.messaging:rcs: 1% user + 1% kernel / faults: 38 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.3% 3509/com.android.systemui: 2.3% user + 0% kernel / faults: 55 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3509/ndroid.systemui: 0% user + 1.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3662/RenderThread: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3664/SysUiBg: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.4% 6641/kworker/X26:11-kverityd: 0% user + 2.4% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.4% 6727/kworker/X26:12-kverityd: 0% user + 2.4% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.4% 8364/kworker/X26:0-kverityd: 0% user + 2.4% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.4% 8935/kworker/X26:2-kverityd: 0% user + 2.4% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.5% 11695/kworker/u24:4-ufs_clkscaling_0: 0% user + 2.5% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.5% 13612/com.google.android.gms.persistent: 2.5% user + 0% kernel / faults: 525 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 13991/binder:13612_A: 1.2% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 15231/binder:13612_C: 1.2% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.6% 17098/com.beeper.android: 1.3% user + 1.3% kernel / faults: 50 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 17348/pool-18-thread-: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 17349/pool-18-thread-: 1.3% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 17868/pool-17-thread-: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 2.6% 20175/kworker/u24:14-adb: 0% user + 2.6% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 6.3% 26058/kworker/u24:9-ufs_clkscaling_0: 0% user + 6.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 13/rcuog/0: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 15/migration/0: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 19/ksoftirqd/1: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 23/rcuop/1: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 44/rcuog/4: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 45/rcuop/4: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 59/rcuop/6: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 66/rcuop/7: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 350/bcc_kthread: 1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 352/usbtemp_kthread: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 812/loop10: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1051/statsd: 0% user + 1% kernel / faults: 13 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1064/Binder:statsd: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1052/netd: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 5695/binder:1052_4: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1201/android.hardware.wifi@1.0-service: 0% user + 1% kernel / faults: 10 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 3349/wifi@1.0-servic: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1222/vendor.qti.hardware.display.composer-service: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1402/surfaceflinger: 1% user + 0% kernel / faults: 1 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1402/surfaceflinger: 1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1671/app: 1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1676/surfaceflinger: 0% user + 1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1% 1754/com.zhiliaoapp.musically: 0% user + 1% kernel / faults: 5 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3383/com.google.android.apps.photos: 1.1% user + 0% kernel / faults: 125 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 3395/Jit thread pool: 1.1% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.1% 4073/com.android.phone: 1.1% user + 0% kernel / faults: 6 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 4141/com.oplus.nas: 0% user + 1.2% kernel / faults: 18 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 21795/binder:4141_8: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 5492/irq/17-4520300.: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 6463/hans: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 6464/hans: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 22724/binder:6463_5: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 11833/kworker/1:2H-fsverity_read_queue: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 13683/co.mediatorium.explorecroatia: 1.2% user + 0% kernel / faults: 1 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 13729/kworker/7:4H-kblockd: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 14979/kworker/0:2H-kblockd: 0% user + 1.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 15888/com.microsoft.office.outlook: 1.2% user + 0% kernel / faults: 3 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.2% 15965/Thread-12: 1.2% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 17685/kworker/u25:2-dwc_wq: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 18078/kworker/X26:7-kverityd: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 18218/logcat: 0% user + 1.3% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 18623/com.oplus.cosa: 0% user + 1.3% kernel / faults: 1 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 18890/ConnectivityThr: 1.3% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 1.3% 20665/com.google.android.apps.maps: 0% user + 1.3% kernel / faults: 12 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: +0% 18369/Background_2173: 0% user + 0% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.1% 24148/com.fitbit.FitbitMobile: 3.1% user + 0% kernel / faults: 2 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.1% 22080/binder:24148_A: 0% user + 3.1% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.2% 28519/kworker/X26:5-kverityd: 0% user + 3.2% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.3% 29726/com.ftw_and_co.happn: 3.3% user + 0% kernel / faults: 2 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.5% 32443/com.oplus.onet: 0% user + 3.5% kernel / faults: 40 minor 07-15 21:10:50.627 2142 18316 E ActivityManager: 3.5% 32462/binder:32443_3: 0% user + 3.5% kernel 07-15 21:10:50.627 2142 18316 E ActivityManager: 61% TOTAL: 20% user + 34% kernel + 2.5% iowait + 2.8% irq + 1.1% softirq ```
bjarnekrottje commented 1 month ago

Alright, good to hear! Hmm, that's unfortunate you were unable to reproduce the issue. I have a OnePlus Nord 3 CE Lite, outside the already mentioned information above in the first message, maybe this information might help:

I can't really think of any other relevant information which could help in this case. Do you maybe have suggestions on what information might be relevant otherwise?

dshokouhi commented 1 month ago
  • I do have quite some apps installed (303 according to the Play Store) > Might it have something to do with the time HA takes to load all the app names and having it time out or something?

thats one of hte suspicions we do need to load a list of apps for teh allow list as most users dont know package names.

dshokouhi commented 1 month ago

in the meantime I suggest using the package attribute of the sensor to filter out responses you dont care for. That is actually how the allow list works for this sensor. The API only returns the next scheduled alarm and there can only be 1 at a time so we skip updates not in the allow list.

bjarnekrottje commented 1 month ago

Alright, thank you very much for the temporary workaround and the explanation and reasoning behind it. I will do that for now. Is there anything I can do in the meantime to help you looking into why the timeout occurs and how this can be fixed? Thanks you very much in advance!