Skip to content

[Linux] Resolve connected phone #197

Closed
NL-TCH wants to merge 1 commit intokavishdevar:mainfrom
NL-TCH:add-phone-name-to-UI
Closed

[Linux] Resolve connected phone #197
NL-TCH wants to merge 1 commit intokavishdevar:mainfrom
NL-TCH:add-phone-name-to-UI

Conversation

@NL-TCH
Copy link
Copy Markdown
Contributor

@NL-TCH NL-TCH commented Aug 25, 2025

image quite a lot of code for the name of the connected phone. the lookup of the name is in cache, and bluetooth-resolving

i would totally get it if you guys think this is over-engineered

@NL-TCH
Copy link
Copy Markdown
Contributor Author

NL-TCH commented Aug 25, 2025

log:

Librepods:  PHONE_MAC_ADDRESS environment variable set to:  "94:45:60:7C:D8:D5" 
Librepods:  Attempting to resolve name for device:  "94:45:60:7C:D8:D5" 
Librepods:  Trying BlueZ D-Bus interface with path:  "/org/bluez/hci0/dev_94_45_60_7c_d8_d5" 
Librepods:  Trying alternative BlueZ method... 
Librepods:  Trying bluetoothctl command... 
Librepods:  Found name via bluetoothctl:  "Pixel 8 Pro" 

@kavishdevar
Copy link
Copy Markdown
Owner

sorry, you're right. i think this can be done by asking the phone when connecting, or just using dbus. having 2 fallback methods might not be necessary.

what do you think, @tim-gromeyer?

@tim-gromeyer
Copy link
Copy Markdown
Contributor

I think the best solution would be to make the dbus implementation work, as this would work with flatoak later on

@kavishdevar
Copy link
Copy Markdown
Owner

kavishdevar commented Oct 1, 2025

Actually, why did we need the name of the device in the first place? Also, this entire relay thingy will now be deprecated in favor of having actual multi-device connectivity with #202. (sorry, but not currently accepting PRs for implementing that in Linux because I haven't documented the data exchange needed for it, just implemented it in Android while I was experimenting. And, I don't want it an AI to copy it from Android as-is.)

feel free to reopen if it seems important to you!

@kavishdevar kavishdevar closed this Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants