IssueTracker

To the reporter: this error is related to the class NotificationsViewModel. I'm trying to figure out exactly how this could happen, but haven't quite gotten there yet. The error seems to imply that the class's constructor is marked with @AssistedInject, but potentially also with @Inject (even though that wouldn't build).

Would you mind sharing some details about how exactly this view model is using Dagger attributes?

(I have a potential fix I can make regardless, but it's always helpful to actually understand the root cause.)

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Narwhal | 2025.1.1 Canary 3
• Android Gradle Plugin 8.11.0-alpha03

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

Can you please send us a bug report?

Bug report for the "doesn't work" case.

• Go to Settings -> About Phone -> Tap on Build number seven times on the build number to enable a new Settings item, Developer options.
• Go to Settings ->Developer options -> Enable USB debugging > Toggle On
• Enable Settings -> Developer options -> Enable Bug Report shortcut > Toggle On
• Once the issue is reproduced: Go to Settings -> Developer options -> Click on take bug report or Press Power button and then choose Bug Report from the Power down menu.
• Wait for some time until the bug report is collected. It takes around 3 to 4 minutes to collect the Bug Report.

And then you can send us the bug report.

I don't see any CDM related logs in the bug report. I guess after you've enabled Bug Report, you'd need to reproduce the issue again so the bug report can catch the logs.

That might be the point. I am seeing the same behavior on a Pixel 6 with Android 15, but it does not happen everytime. Sometimes after a restart the CompanionDeviceManager starts doing its job right away, but sometimes it will not do anything at all. Meaning you can turn the BLE device on or off as often as you like and nothing from CDM_* shows in the logs. The only thing you get once after boot-up is this:

2024-11-15 08:11:25.117  1597-1597  AconfigFlags            zygote64                             V  Read Aconfig default flag value com.android.internal.telephony.flags.minimal_telephony_cdm_check = true
2024-11-15 08:11:28.709  1597-1597  CDM_Compan...ortManager zygote64                             I  Registering OnTransportsChangedListener
2024-11-15 08:11:28.710  1597-1597  CDM_Associ...nDiskStore zygote64                             I  Reading associations for user 0 from disk.
2024-11-15 08:11:28.712  1597-1946  CDM_ObservableUuidStore zygote64                             I  Reading ObservableUuid for user 0 from file=/data/system_de/0/observing_uuids_presence.xml
2024-11-15 08:11:28.712  1597-1946  CDM_ObservableUuidStore zygote64                             D  File does not exist -> Abort
2024-11-15 08:11:30.574  1597-1597  CDM_BleDeviceProcessor  zygote64                             I  startBleScan()
2024-11-15 08:11:31.101  1597-1682  CDM_Inacti...valService zygote64                             I  Scheduling the Association Removal job
2024-11-15 08:11:33.271  2863-2948  AconfigFlags            <pre-initialized>                    V  Read Aconfig default flag value com.android.internal.telephony.flags.minimal_telephony_cdm_check = true
2024-11-15 08:12:11.840  1597-1695  CDM_Compan...gerService zygote64                             D  onUserUnlocking...

In that state I do not think that anything would show up in the bugreport if you just capturing the moment when the BLE device is turned on or off. If you disable and reenable Bluetooth, however, the CDM starts doing its job and launches the associated app (in this case org.staacks.alpharemote):

2024-11-15 08:19:39.438  1597-1597  CDM_BleDeviceProcessor  zygote64                             I  stopBleScan()
2024-11-15 08:19:41.660  1597-1597  CDM_BleDeviceProcessor  zygote64                             I  startBleScan()
2024-11-15 08:19:42.301  1597-1597  CDM_Device...eProcessor zygote64                             I  onBleCompanionDeviceFound associationId( 113 )
2024-11-15 08:19:42.301  1597-1597  CDM_Device...eProcessor zygote64                             I  onDevicePresenceEvent() id=[113], event=[0]...
2024-11-15 08:19:42.301  1597-1597  CDM_CompanionAppBinder  zygote64                             I  Binding user=[0], package=[org.staacks.alpharemote], isSelfManaged=[false]...
2024-11-15 08:19:42.309  1597-1597  CDM_Device...eProcessor zygote64                             I  notifyCompanionDevicePresenceEvent userId=[0], packageName=[org.staacks.alpharemote], event=[ObservingDevicePresenceResult { Association Id= 113,ParcelUuid= null,Event= 0}]...
2024-11-15 08:19:42.309  1597-1597  CDM_Device...eProcessor zygote64                             I  legacyNotifyDevicePresenceEvent() association=[id=113, addr=00:9D:6B:B9:06:16, pkg=u0/org.staacks.alpharemote], isAppeared=[true]
---------------------------- PROCESS STARTED (12525) for package org.staacks.alpharemote ----------------------------
2024-11-15 08:19:42.537  1597-12519 CDM_Compan...eConnector zygote64                             D  onServiceConnectionStatusChanged() {org.staacks.alpharemote/org.staacks.alpharemote.service.AlphaRemoteService} connected=true
2024-11-15 08:19:42.972  1597-1597  CDM_Device...eProcessor zygote64                             I  onBluetoothCompanionDeviceConnected: associationId( 113 )
2024-11-15 08:19:42.972  1597-1597  CDM_Device...eProcessor zygote64                             I  onBluetoothCompanionDeviceConnected: associationId( 113 )
2024-11-15 08:19:42.972  1597-1597  CDM_Device...eProcessor zygote64                             I  onDevicePresenceEvent() id=[113], event=[2]...
2024-11-15 08:19:42.972  1597-1597  CDM_Device...eProcessor zygote64                             I  UserId=[0], packageName=[org.staacks.alpharemote] is already bound.
2024-11-15 08:19:42.972  1597-1597  CDM_Device...eProcessor zygote64                             I  notifyCompanionDevicePresenceEvent userId=[0], packageName=[org.staacks.alpharemote], event=[ObservingDevicePresenceResult { Association Id= 113,ParcelUuid= null,Event= 2}]...
2024-11-15 08:19:42.972  1597-1597  CDM_Device...eProcessor zygote64                             I  legacyNotifyDevicePresenceEvent() association=[id=113, addr=00:9D:6B:B9:06:16, pkg=u0/org.staacks.alpharemote], isAppeared=[true]
2024-11-15 08:19:42.972  1597-1597  CDM_BleDeviceProcessor  zygote64                             I  stopBleScan()

But as I said: Sometimes you reboot and everything is fine without the need to restart Bluetooth. The logs before turning on the BLE device are almost identical to the fail state:

2024-11-15 08:21:52.896  1470-1470  AconfigFlags            zygote64                             V  Read Aconfig default flag value com.android.internal.telephony.flags.minimal_telephony_cdm_check = true
2024-11-15 08:21:55.927  1470-1470  CDM_Compan...ortManager zygote64                             I  Registering OnTransportsChangedListener
2024-11-15 08:21:55.928  1470-1470  CDM_Associ...nDiskStore zygote64                             I  Reading associations for user 0 from disk.
2024-11-15 08:21:55.929  1470-1939  CDM_ObservableUuidStore zygote64                             I  Reading ObservableUuid for user 0 from file=/data/system_de/0/observing_uuids_presence.xml
2024-11-15 08:21:55.930  1470-1939  CDM_ObservableUuidStore zygote64                             D  File does not exist -> Abort
2024-11-15 08:21:57.648  1470-1470  CDM_BleDeviceProcessor  zygote64                             I  startBleScan()
2024-11-15 08:21:58.061  1470-1649  CDM_Inacti...valService zygote64                             I  Scheduling the Association Removal job
2024-11-15 08:21:59.971  2849-2951  AconfigFlags            zygote64                             V  Read Aconfig default flag value com.android.internal.telephony.flags.minimal_telephony_cdm_check = true
2024-11-15 08:22:00.039  2849-2951  AconfigFlags            zygote64                             V  Read Aconfig default flag value com.android.internal.telephony.flags.minimal_telephony_cdm_check = true
2024-11-15 08:22:15.820  1470-1680  CDM_Compan...gerService zygote64                             D  onUserUnlocking...
2024-11-15 08:22:15.909  1470-1680  CDM_Compan...gerService zygote64                             I  onUserUnlocked() user=0

(AconfigFlags appears twice when it works and onUserUnlocked() is missing when it does not work. Checked multiple reboots.)

the issue might be CDM initiating scans after PHASE_SYSTEM_SERVICES_READY. This could be unreliable. We've changed to scan after PHASE_BOOT_COMPLETED which should have been released in 24Q4.