Power State Conflict between Google Drive for Desktop & Battery Toolkit v1.8:

[mzblues1]

Developer: Battery Toolkit v1.8:

The following is a technical brief that explains that there are two separate paths to resolve the issues, but they are currently mutually exclusive (you can't have one setting that fixes both at the same time).

Technical Report: Power State Conflict between Google Drive & Battery Management:

Device: MacBook Pro (Apple Silicon M3 Pro)
OS: macOS Sonoma/Sequoia
Software involved: Google Drive for Desktop & Battery Toolkit v1.8

The Issue:
There is a conflict between the Google Drive launchd daemon and third-party charging limiters during sleep/wake transitions. The app enters a "zombie" state (processes are active but the UI/Icon is missing) depending on the power source and specific macOS Energy settings.

The "Mutually Exclusive" Workarounds:
We have discovered that a fix exists for both scenarios, but they require different, conflicting system configurations:

1. To Fix "Plugged-In" (AC Power) Mode:
   Setting: Enable "Prevent automatic sleeping on power adapter when the display is off" AND set "Turn display off on power adapter" to Never.
   Result: Google Drive survives overnight sleep while plugged in and limited to 80%.
   Failure: This configuration does not fix the issue when the laptop is on battery power.

2. To Fix "Battery" (Unplugged) Mode:
   Setting: Set "Wake for network access" to Always AND set "Low Power Mode" to Never.
   Result: Google Drive maintains its handshake while on battery.
   Failure: This configuration breaks the "Plugged-In" fix, causing the icon to vanish when the charger is connected during sleep.

Technical Conclusion for Developers:
The Google Drive File Provider extension is failing to re-initialize because launchd is receiving conflicting "Power State" signals. When a third-party daemon (Battery Toolkit) is managing SMC charging registers, it creates a "non-standard" power profile that causes Google Drive to hang during DarkWake unless the system is forced into a specific, high-energy "Wake for Network" or "Prevent Sleep" state.

Apple Tech Support mentioned "launchd":
launchd is the "parent" that starts Google Drive. When you close the lid, launchd looks at your settings. If it sees "Battery + Low Power Mode," it tells Google Drive: "Stay asleep, don't talk to the network." If you are "Plugged In + Prevent Sleep," it says: "Keep running." The conflict happens because Battery Toolkit makes the Mac think it's in one state while the hardware is actually in another.

I hope this is helpful towards your future development.

Regards,

Marty

[mhaeuser]

The conflict happens because Battery Toolkit makes the Mac think it's in one state while the hardware is actually in another.

I don’t think this is true and the LLM didn’t explain why it would be either… sounds like a Google Drive bug to me.

[mzblues1]

Just trying to help with what I've experienced. Wasn't claiming Battery Toolkit specifically was the issue, as I've shared the same information with Google as well. Just suggesting there is a conflict happening.

I suggest installing GD for Desktop on a Silicone Mac and trying it for yourself to see if you experience the same...for your information only.

[yonggodlikean]

YES, I meet the same situation , my Mac can't charge although the battery is lower than the setting to charge on, I want to know how to solve it？

[mhaeuser]

@yonggodlikean I don’t think that is what this issue is salt and I can’t really say much without any details.