Quote:
|
If possible I'd not mess with the recovery partition. It's your insurance against bricks, unless you don't mind opening the device up to handle the SD card directly?
|
I already bricked it once.
Turning the debugging information on for udev made it so my AuraHD didn't want to boot; and for some reason, didn't want to go into recovery mode either. It shouldn't have affected recovery mode, but I ended up pulling the screen face off, to get to the four corner screws, so I could remove the motherboard -- and also removing the SD card, and re-edit the udev because I couldn't figure out how to get it to enter recovery mode the normal way.
I never expected something as innocent as turning debug mode on in udev to lock up a system...
But that's specifically why I bought the AuraHD and Glo, and an SD card reader; as opposed to a plain Aura, or AuraH20, etc. or even a kindle. Because those other ones either don't advertize having an internal SD card, and I'm a hacker at heart and I know there are risks... (My first thread here was about a Sony reader, which I irreversibly bricked.)
In fact, I'm looking at making a new face-plate for my AuraHD anyway; so taking it apart didn't bother me. (It's glued/taped fairly strongly, so removing it is likely to stress the bezel and I don't recommended doing that for everyone. The Glo's are much safer to take apart. )
The factory made bezel overlaps the edge of the screen slightly, so that the first character when printed at the very edge of the screen is partially obscured by the Bezel. (In fact, when I use 8x12 pixels as a letter size -- it obsucres one whole letter -- I have 30/30 vision -- but you might need a magnifying glass to see something that small. It makes for up to 180x90 character display terminal ) and I find obscured edges annoying -- and my kids didn't wan't the AuraHD -- becuase the extra glossy black plastic shows fingerprints really badly and they thought that makes it look dirty. (Which is fine with me, as the Glos's cost less.)
So -- I'm thinking that I'll make a custom bezel out of a silicone urethane mix for my AuraHD since I don't like the fingerprints much either and then I can thumb my nose at my kids. But I do like the higher resolution screen.
As far as the Orientation, whenever I read the information for the rotation orientation from the framebuffer on the AuraHD -- it returns a number 0..3, which is different from the number written to it in the first place to set the orientation. So the read and the write are simply different numbers; but it's consistently wrong, not random -- which is why If you look in the source code I gave at the beginning of the thread -- I exclusive ored that number with 2, so that 0<-->2 and 1<-->3. eg: it causes an erroneous 180 degree flip to correct so that the screen re-loads in the same orientation it was saved in.
Some devices both read and write the same number, some read one set of numbers but write another.
That was my first clue that there was something quite different between the Glo and the AuraHD.
