View Single Post
Old 12-27-2012, 08:01 PM   #238
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
There are two potential answers to this issue:
  1. Block communications with Amazon.
  2. Disable the cause of the communications.

(2) requires learning a lot about the internals of the firmware.
I.E: Will be time consuming (probably by a lot of people).

(1a) Blocking can be implemented on a person's home network
(1b) Or within the Kindles' own firewall.

I posted about (1a) today, will follow with an update of (1b) RSN.
Both based on the Kpw, v-5.3.1 firmware.
knc1 is offline   Reply With Quote