View Single Post
Old 06-10-2017, 04:57 PM   #9
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,514
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
Tried a bit more.

I put completely different image instead of critbatt.png and it turns out that the first squeezed one is 'stuck' somewhere in cache - is still shows up in the same way instead of the new one, only the fist half is visible, but it is squeezed to the whole screen real estate.

I also tried to put a tricky image which has all the necessary information 'squeezed' only to the first half in width, so I thought when Kindle squeeze it again it will look normal. However it didn't work probably due to the suspicion in the previous paragraph.

Any clues where I should look for this 'low power cache' and the reasons why it stuck?

P.S.
Also I am thinking about the case that these folders of 'opt/amazon/low_level_screens/$locale$/600x800/' serve a container which Kindle grabs boot pictures but only for the first time.
A contrary argument is that iterative replacement of 'reboot.png' was always working - I got it working after some trials. So now I am a bit confused.

Would appreciate any help.
mergen3107 is offline   Reply With Quote