| Issue 5: | Run as a Service - Enhancement |
1 of 9
Next ›
|
| 1 person starred this issue and may be notified of changes. | Back to list |
Probably you can consider running this application as a service (background) to monitor connections only when you see Wifi/3G enabled and option to disable/enable this service Also it would be great to have historical data of connections by id/appname in a chart would be nice addition. I can help you submitting patch/code. Please let me know if you are interested. Thanks, Umakanth
Mar 27, 2012
Thanks , Agree. The Following things could be implemented. * As a Service ( foreground application ) a) Monitor Connections/Iptables Log only if Wifi/3G enabled b) Write output logs to SDcard/Internal memory or Store it in a DB ( for backup and restore purpose) c) Broadcast log entry as a toast ( I would suggest not to send notifications to bar) d) Whitelist application? ( I think you already have something like this) * As a Viewer a) on startup, retrieves user-defined entries from service's log file or DB to load historical data; b) listen for broadcasted log entries for current data c) presents the data in multiple forms: log, per app, graphs, timeline d) Iptables rules viewer if any ( people who use iptables based softwares like DroidWall,Avast,LBE) Other suggestions I would like to mention here, * ICS Theme - People really like any app in ICS theme :) * App name as "Firewall Monitor" or something fancy - I personally feel instead of iptables log , if you could change the app name to common names like "Firewall Monitor" it will definitely get attention. I may sound silly. just my thought, please ignore it if you don't like it :) and I'll update it here if anything. Thanks for considering my ideas, I can help you in testing and development as well. Let me know.
Mar 29, 2012
(No comment was entered for this change.)
Labels:
-Priority-Medium Priority-Critical
Apr 5, 2012
Almost done! Expect another release by April 8th.
Status:
Started
Apr 11, 2012
Done in 0.7.0 -- release expected by 4/14.
Status:
Done
|
These are both excellent suggestions. It is planned to divide the app into two parts: 1) a small tight and efficient background service (run as foreground so the Android system does not kill it) that strictly does three things: a) monitor iptables log; b) output log to a file; c) broadcast log entry 2) an simple app that does the following: a) on startup, retrieves user-defined entries from service's log file to load historical data; b) listen for broadcasted log entries for current data c) presents the data in multiple forms: log, per app, graphs, timeline What are your thoughts?Owner: pragma78@gmail.com
Labels: -Type-Defect Type-Enhancement