0x192 / 0x192/universal-android-debloater

wont display on BLU view2

未關閉
#501 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Rust
星號
19.9k
分支
1.1k
PR 合併指標
30 天內沒有已合併 PR

描述

I confirmed i have connection via command line

`C:\adb>adb devices
List of devices attached
1060339021022681 device`

a notice even pops up on the device regarding allowing debugging (which is already enabled). but the GUI still states no devices connected

now, i dont know if it matters, it does recognize the device with a couple of beeps and pop ups at the systray notification area, about wanting to view files (So i know Im indeed connected).

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

The issue is that ADB recognizes the device via command line but the GUI does not show it. Start by examining the device detection logic in the Rust codebase, likely in a module handling ADB communication. Look for where `adb devices` output is parsed and how the GUI updates its device list. Check for any platform-specific handling for BLU View2. Run the GUI in debug mode to see logs when connecting the device.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
android, rust
領域
cli, desktop, tooling
Issue 類型
缺陷
難度
3/5
預估耗時
1-2 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。