View Single Post
Old 03-02-2013, 06:21 AM   #65
dsmid
Linux devotee
dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.dsmid ought to be getting tired of karma fortunes by now.
 
dsmid's Avatar
 
Posts: 598
Karma: 2069047
Join Date: Feb 2011
Device: Kindle 3, Kindle 4B, Kindle PW2
I have an idea how to stop pushed updates even on KPW and KT but I can't implement it because I don't have any KPW or KT device.

In case someone wants to give it a try:
  1. First you need otaupd to release DBus service name com.lab126.ota. That's easy: search for com.lab126.ota in the binary and replace it by e.g. com.lab126.pta (rhymes with PITA).
  2. Then code a replacement DBus service that registers name com.lab126.ota for itself. Most of the time it would just pass all calls to com.lab126.pta via DBus but when a suspicious request is detected (one that looks like pushed update), it would just log it instead.
    You can use any DBus stack for that, I prefer QtDBus as it worked OK on Kindle 3 last time I tried.
dsmid is offline   Reply With Quote