Corrupted Image on Eink Display
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 207
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Has one encountered problems with corrupted images on the eink display? Its seems like I am getting corrupted images quite often. I don't think its a hardware problem since I am able to have a standalone program that consistently displays an image on the eink from the ESP32 memory.
I am suspecting its the HTTP get request that receives corrupted bytes from the sever, but I don't know how to verify that. Any advice on this?
Thanks in advance!
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
No source files, tests, or entry points are named in the issue. Start by locating the ESP32 HTTP image-fetching and e-ink display code, then reproduce the corruption and compare the received image bytes with the standalone display input. Done means identifying whether transfer or display handling causes the corruption and adding a verified fix or regression check.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100