View Single Post
Old 07-07-2016, 10:41 AM   #23
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by jprince View Post
The graphics I get pretty much match theirs—filling the upper right of the screen, as if it were using graphics intended for the Kindle PW version with less DPI.
The dimensions are hardcoded as determined by the device serial number and/or PCB ID. These device identifiers are "idme vars" stored in a hidden area you may access in diags or with the "idme" command. It is possible that they got damaged, but more likely that the firmware is looking for them in the wrong location. Those screen artifacts in the photos look scarily like a broken screen, but no need to panic in this case. We can fix this (with serial port, or even simpler).
geekmaster is offline   Reply With Quote