mirror of
https://github.com/tytydraco/LADB.git
synced 2026-04-27 00:15:59 +03:00
[GH-ISSUE #86] Unprompted ChromeOS interaction #64
Labels
No labels
bug
documentation
enhancement
enhancement
good first issue
help wanted
pull-request
question
question
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LADB#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @boognish-rising on GitHub (Oct 12, 2022).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/86
I thought that I had made mention of this previously but I don't see any mention of it in any issues or even comments so I could be wrong and if I'm not I don't know where I made mention of it but many times now when I've gone to use LADB instead of it trying to initiate wireless debugging on my phone (Google Pixel 6 Pro Android 13) It seems to somehow be communicating with my Pixelbook, which is obviously a completely separate device. I'm at a loss for why this is happening. I do have the Pixelbook connected to my Pixel via the Phone Hub feature/functionality of ChromeOS, but that's just connecting via Bluetooth as far as I know but even if it was connecting via a Wi-Fi connection or even over the network, I don't see why that would cause this to happen. Am I missing something or is this completely weird behavior?
@teou1 commented on GitHub (Oct 14, 2022):
I'd say it sounds like google bug with chrome os and the phone hub, which is quite buggy and does not always connect on my Chomeos 105 and pixel4a A13 setup. However, i have not enabled adb on the chromebook, i guess that's the difference.
If i were you i'd try 2 things: manually starting witeless debug on the phone before running ladb, and maybe turning off bluetooth or/and wifi on the Chromebook until ladb connects.
@ShadowFlare commented on GitHub (Oct 14, 2022):
Sounds related to #61 that I opened.
@boognish-rising commented on GitHub (Oct 14, 2022):
You're absolutely right. Sounds identical, even. My fault. I did a search but I searched for "Chromebook" and "ChromeOS" and didn't think it was an issue that extended to network devices beyond Chromebooks/Chrome OS specifically.
That said, feel free to either close this as a duplicate or merge it or whatever you think is necessary or more conducive to keeping things tidy around here @tytydraco
Apologies for missing #61 that @ShadowFlare mentioned/started... I'll keep an eye on that for progress/new developments, etc
@tytydraco commented on GitHub (Oct 15, 2022):
Cool cool:
Please refer to https://github.com/tytydraco/LADB/issues/61