Automated kiosk log uploading should also grab ARC++ logs |
||||||
Issue descriptionWe should also upload the Android system logs (make sure we sanitize them as we do the cros logs). Additionally we should maybe touch base with the privacy team to make sure they don't have any concerns over the information that ends up in the ARC logs.
,
May 27 2016
,
May 31 2016
I grabbed the logs from my ARC++ enabled dogfood device. It's a little hard for me to tell which part is from Android in the log. Can someone help point this out? Since Vadym is taking a look at kiosk mode in general, I'm adding him to the bug.
,
May 31 2016
You grabbed the wrong file. What you need is: * Go to chrome://net-internals * Click on "ChromeOS" [sic] in the left column * Click "Store Debug Logs" This will dump a zip file of various logs into your Downloads directory.
,
May 31 2016
,
Jun 1 2016
That's A LOT of files to look at. Can someone point out what's the delta? I can attach the files here for Vadym to examine.
,
Jun 6 2016
The easiest thing to do is to grab logs from two devices, one with and one without ARC. Then you will know which logs are ARC-only.
,
Jun 7 2016
,
Jun 8 2016
Can someone from the managed device team do this and attached sample log files here? It's just easier for the people who already know how than for us to figure this out.
,
Nov 10 2016
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by bartfab@chromium.org
, May 25 2016