Hi. First, thanks for all the work you do here, I've been able to make the most out of my kindle because of your hacks. Unfortunately now the screen on my k3 has stopped working.
A while ago I got another k3 from a family member in the same condition as mine is now. Both are responsive as diagnosed by the led and turning on the voice guide, and USB access. Also, mine is rooted and has the USBnetwork hack installed (and other hacks too). Apart from the screen they both seem perfectly fine. Also, the screens look fine too! Could they might still be broken even though I can't see it, in which case I'm out of luck...
When I first got the old one, and mine was still fine, I disassembled them and swapped the screens to check if buying a new screen would help (I had already cracked mine's original screen and successfully replaced it). But neither the old one with mine's then fine screen, nor mine with the old one's frozen one worked. This was weird. I expected the old one to work with a functional screen, but it didn't, so I didn't buy another screen for it, since I was still using mine. (Maybe the two screens were not compatible or something, which would mean that I got lucky when replacing the original cracked screen).
Now that one has frozen. I've rebooted it many times with no luck. I think I got into diags mode by holding the HOME button when powering up, and then out of it with x (googled for screenshot of diags mode), with no change in the screen. I didn't want to use the ENABLE_DIAGS method because I might get stuck with no usb mode, and besides, I can run the diags via ssh anyway, right?
Tried clearing the screen with `eips -c`, but no luck. Tried running /opt/eink/scripts/diag and I get:
Quote:
eips: pixel_in_range> (612, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (636, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (648, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (660, 580) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 580) pixel not in range (0..600, 0..800)
|
I haven't done a factory reset on mine because I would loose all the hacks, right?, and I don't know if it would help since it didn't help the other one.
Any ideas on what might be wrong? Are the screens physically dead even though I can't see damage? Anything else I can run to diagnose the problem?
Thank you very much, sorry for the long post.