Project

General

Profile

Actions

New Feature #10738

closed

Screen usage violate policy

Added by Sandaru Daminda 8 months ago. Updated 3 months ago.

Status:
Closed
Priority:
High
Start date:
28/04/2024
Due date:
10/05/2024
% Done:

100%

Estimated time:
Device Type:
Component:
Android Agent
Type:
Android

Files

Actions #1

Updated by Sandaru Daminda 7 months ago

  • Due date changed from 28/02/2024 to 21/03/2024
Actions #2

Updated by Viranga Gunarathna 6 months ago

  • Project changed from product-uem 6.1.0 GA to product-uem 6.2.0 GA
Actions #3

Updated by Sandaru Daminda 5 months ago

  • Due date changed from 21/03/2024 to 10/05/2024
  • Start date changed from 21/02/2024 to 28/04/2024
Actions #4

Updated by Sandaru Daminda 5 months ago

  • Tracker changed from Bug to New Feature
  • Subject changed from Improve Screen usage policy and accuracy to Screen usage violate policy

Updated by Arshana Atapattu 3 months ago

The specified time on policy does not honor on the device side.
EX: let's say gmail app was set to 30 mins usage time and on device side when we use only around 1-2 mins app gets blocked.
this happened on all apps.

On Wikipedia app:
Started time: 18.35 [1]
Blocked time: 18.372

On Gmail app:
Started time: 18.43 [3]
Blocked time: 18.44 [4]

Payload of the policy: [5]

Issue 2: Apps period were configured as per day. But after a day, apps are still not accessible(blocked)

[1]
[1]

[2]
[2]

[3]
[3]

[4]
[4]

[5] {
"policyName":"App usage screen usage",
"description":"App usage screen usage",
"active":true,
"compliance":"enforce",
"ownershipType":null,
"policyType":"GENERAL",
"profile":{
"profileName":"App usage screen usage",
"deviceType":"android",
"profileFeaturesList":[ {
"featureCode":"APP_USAGE",
"deviceType":"android",
"content":{
"isNetworkUsageEnabled":false,
"isBlockMeteredConnectionEnabled":false,
"isScreenUsageTrackingEnabled":true,
"appsScreenUsageData":[ {
"packageName":"com.google.android.youtube",
"allowedTimeType":"Minutes",
"periodTimeType":"86400",
"allowedTime":"10"
}, {
"packageName":"com.android.chrome",
"allowedTimeType":"Minutes",
"periodTimeType":"86400",
"allowedTime":"10"
}, {
"packageName":"org.wikipedia",
"allowedTimeType":"Minutes",
"periodTimeType":"86400",
"allowedTime":"20"
}, {
"packageName":"com.google.android.gm",
"allowedTimeType":"Minutes",
"periodTimeType":"86400",
"allowedTime":"30"
}, {
"packageName":"com.facebook.katana",
"allowedTimeType":"Minutes",
"periodTimeType":"86400",
"allowedTime":"20"
}
],
"isScreenUsageNotificationsEnabled":true
},
"correctiveActions":[

]
}
]
},
"deviceGroups":[ {
"id":59,
"name":"Test Devices"
}
],
"roles":[
"ANY"
],
"users":[
]
}
Actions #7

Updated by Kavin Prathaban 3 months ago

  • Status changed from QA Reject to QA
Actions #8

Updated by Thilina Sandaruwan 3 months ago

  • Component set to Android Agent
Actions #9

Updated by Arshana Atapattu 3 months ago

  • Status changed from QA to Needs Improvement

There is a issue with time interval.
When a app was allocated 5mins of screen time and when app exceed the allocated time app gets blocked.
But the app should be unblocked on the next day(12am)(Consider per day, per month). Currently this is not refreshing(allocated quota) happening.

Actions #10

Updated by Kavin Prathaban 3 months ago

  • Status changed from Needs Improvement to QA

Arshana Atapattu wrote in #note-9:

There is a issue with time interval.
When a app was allocated 5mins of screen time and when app exceed the allocated time app gets blocked.
But the app should be unblocked on the next day(12am)(Consider per day, per month). Currently this is not refreshing(allocated quota) happening.

Fix added for the above issue, and improvements on calculating screen usage:
https://repository.entgra.net/proprietary/android-agent/pulls/90

Actions #11

Updated by Arshana Atapattu 3 months ago

  • Status changed from QA to QA Accept

feature is working

Actions #12

Updated by Arshana Atapattu 3 months ago

  • Status changed from QA Accept to Closed

Closing due to QA accept

Actions

Also available in: Atom PDF