librepods-org / librepods-org/librepods
Not working with Hyperos 2.0 rooted Xiaomi EU rom
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 29.9k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I tried both https://github.com/kavishdevar/librepods/actions/runs/22353095111 and https://github.com/kavishdevar/librepods/actions/runs/22353150985 and both sometimes say that the airpods are not connected, whenever I click the gear icon it sometimes says 0% battery on both airpods and the case. On https://github.com/kavishdevar/librepods/actions/runs/22353095111 I only get a black screen.
Here are some screenshots of what I see:
I also managed to generate a log file however this is not that straight forward because as you can see I sometimes get the 0% on everything window. I also tried the regular download but I get the error: Setup failed: failed to download radare2 tarball. But as I've seen this is a known thing. I use AirPods pro 3s and a Xiaomi 11 Lite 5G NE with unlocked bootloader and Xiaomi EU HyperOS 2.0 stable ROM installed, rooted with Magisk 30.7 with Zygisk and the Zygisk - LSPosed module installed. Maybe I missed something obvious but I can't think of anything.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report on the Xiaomi 11 Lite 5G NE with Xiaomi EU HyperOS 2.0, Magisk, Zygisk and LSPosed, then inspect the attached airpods_log file and compare the two linked Actions builds. Done should mean the AirPods connection, battery display and screen behavior are reliably corrected or the failure is narrowed to a specific component.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100