Thanks Jeff. I see that's what Settings>Data Usage actually does. But then 
the referenced page is maybe a bit misleading for this purpose. 

Anyway, how to go about being more granular and control uplink (tx) and 
downlink (rx) separately using the same interface.  I would like to void 
editing netd module unless it's my best bet for achieving this. 

On Thursday, January 10, 2013 8:20:13 PM UTC, Jeff Sharkey wrote:
>
> It's called in NetworkStatsService.setUidForeground(), but the counter 
> sets here are purely used for statistical accounting purposes. 
> NetworkPolicyManagerService.updateRulesForUidLocked() is the one that 
> actually enforces rules through setUidNetworkRules(). 
>
> j 
>
> On Wed, Jan 9, 2013 at 6:22 AM, Aspire Belgrade 
> <[email protected] <javascript:>> wrote: 
> > What is the exact effect of setKernelCounterSet() in 
> > NetworkManagementSocketTagger ? 
> > Referenced in: 
> http://source.android.com/tech/datausage/kernel-overview.html 
> > 
> > I was hoping to restrict Backgound Metered Data for a specific UID but 
> > results confuse me as an application was still able to acquire network 
> > connection. Secondly, I can not find usages of this method call in 
> Android 
> > Framework by any higher level APIs. 
> > 
> > Finally, can I see the effects of executing this command by viewing ALOG 
> > from a android/base/core/jni/* functions? Or how should I infer the 
> > proc/net/xt_qtaguid/ctlr interface file? 
> > 
> > I am hoping that someone can point me to the right direction, thanks. 
> > 
> > -- 
> > unsubscribe: [email protected] <javascript:> 
> > website: http://groups.google.com/group/android-porting 
>
>
>
> -- 
> Jeff Sharkey 
> [email protected] <javascript:> 
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to