USB only charging after activation of second user

shiaido

Pixel 10 Pro Stable – USB stuck on charging only (short vibration), no prompt for file transfer or ADB after activating/starting secondary profile (before I started the second Profile it worked without any problem, with any cable)). Owner also affected. Only Works with Galaxy S24 (prompt for USB Mode and DebugMode - if activated - comes), but not with Windows/Linux PC ( Win11 and CachyOS on an XMG Neo 16 E25) . Default USB config toggle + reboot + exploit protection changes don't help. These all with several USB-C to USB-C cables (20Gbps, 240W etc. etc.), Latest stable Build. The only cable that works is an older USB-A to USB-C cable.

shiaido

Tried so far (no effect):
Developer Options → Default USB configuration → File Transfer (toggled multiple times)
USB debugging toggle on/off several times
Exploit protection → USB-C Port → various settings (Allow when unlocked, Charging only when locked, etc.)
Multiple full power-offs + reboots
Connecting to another Android device first (Galaxy S24) as USB controller → no effect when connecting to PC afterwards

userofgos

What exactly is your desired goal for USB functionality? It's not clear in your post.

It isn't recommended to mess around with ADB

Also, if you're not already aware, messing with Developer options is likely the cause of these issues. There are in a hidden menu and called "Developer" options for a reason, they aren't expected to be completely stable, without bugs, and used on a production device.

USB file transfer works without Developer options

See here: https://xcancel.com/GrapheneOS/status/1995687056664830337#m

It weakens security if someone obtains the device unlocked since they can enable and authorize ADB without your PIN/password. Developer options has a PIN/password prompt. This is particularly relevant if you have other profiles which are currently in After First Unlock state.

Having developer options enabled without changing anything in it will only negatively impact things with the device unlocked. ADB being enabled will negatively impact security when it's exposed via USB so not when locked in charging-only while locked mode but it still matters.

There are many ways to reduce security in developer options. Using ADB at all reduces security since you're giving immense access to another computer. ADB should be avoided on a production device. There are many dangerous features in developer options beyond using ADB though.

shiaido

Developer Options enabling USB debugging and/or toggled to File Transfer was one of the tries at least to copy/push files onto the phone:
And as i wrote " no prompt for file transfer " ... the rest following:

My Post on Github:

Device: Pixel 10 Pro
GrapheneOS Version: Stable [202602601]
Trigger: Everything worked perfectly before activating/starting the secondary profile (including MTP, ADB, OTG with any USB-C cable). After activating the secondary profile, USB connection to PC (Windows 11 and CachyOS/Linux) shows only charging (short vibration + charge icon), no prompt for File Transfer, PTP, MIDI or ADB authorization. No USB options appear in notification shade or settings.

Affects both profiles (Owner and Secondary).
Tested with multiple high-quality USB-C to USB-C cables (20 Gbps, 240 W PD etc.).
Works perfectly with another Android device (Galaxy S24): Prompt for USB modes and ADB appears.
Only an old USB-A to USB-C cable partially works (under Linux with Dolphin at ~30 MiB/s).

What I already tested (none of it helped):

Developer Options → Default USB configuration → toggled to File Transfer multiple times
USB debugging on/off toggle (multiple times)
Exploit protection → USB-C Port → tried all available settings (Allow when unlocked, Charging only when locked, etc.)
Multiple full power-offs + wait + reboots
Connecting to another Android device first (Galaxy S24) as USB controller → no change when reconnecting to PC
Multiple high-quality USB-C to USB-C cables (20 Gbps, 240 W PD, etc.)
USB-C cable + USB-A adapter at the PC side → still no prompt

The only cable that partially works is an older USB-A to USB-C cable (under Linux with Dolphin file manager at ₃₀ MiB/s). All modern USB-C to USB-C connections (direct or via adapter) result in charging-only mode with no prompt.

This seems related to Pixel 10 series USB firmware issues (#6641, #6938) but with additional secondary profile trigger.

Steps to reproduce:

Start with clean Owner profile → USB works.
Create and activate secondary profile, logging into it - USB works, but multiple data trasfer errors.
Reboot
Try USB to PC → stuck on charging only, no prompt.

Expected: USB prompt should appear as before.
Actual: No prompt, only charging.

shiaido

Interesting: After deleting the second user, everything works fine like before ...