Thread: Possible new downgrade method
View Single Post
Old 05-16-2022, 04:22 PM   #30
jhowell
Grand Sorcerer
jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.jhowell ought to be getting tired of karma fortunes by now.
 
jhowell's Avatar
 
Posts: 7,118
Karma: 92190133
Join Date: Nov 2011
Location: Charlottesville, VA
Device: Kindles
Quote:
Originally Posted by j.p.s View Post
That (more or less) was already suggested by fonix and warned against by jhowell
because of effects on server interaction (file type delivered, etc).
Kindle apps and devices include the build number in normal interactions with Amazon's servers. They keep track of the most recent build announced by each registered device. That in turn controls a large set of capabilities associated with the device.

I don't know how Amazon treats interactions with a device reporting an unexpected build number. They might retain the capabilities associated with last valid build number received or switch to a default set. In any case it is likely to be reported in an error log somewhere.

Quote:
Originally Posted by j.p.s View Post
And recent results show that the UI can be affected.
Actually I now believe that the UI problem was due to the unexpected firmware downgrade.
jhowell is offline   Reply With Quote