0x192 / 0x192/universal-android-debloater
wont display on BLU view2
- Dominant language
- Rust
- Stars
- 19.9k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
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).
Contributor guide
No contributing guide indexed for this repository
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, rust
- Domain
- cli, desktop, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100