Closed
Bug 1157762
Opened 10 years ago
Closed 10 years ago
Autophone - device issue 2015-04-23 - nexus-5-kot49h-1
Categories
(Testing Graveyard :: Autophone, defect)
Testing Graveyard
Autophone
Tracking
(firefox40 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox40 | --- | affected |
People
(Reporter: bc, Assigned: marcia)
References
Details
nexus-5-kot49h-1 is behaving abnormally. It is taking far too long to run the s1s2tests.
On 2015-04-16 it was taking ~15 minutes.
On 2015-04-17 it was taking ~30 minutes
On 2015-04-18 it was taking ~60 minutes.
mfinkle, snorp: This may be the reason for the performance changes in this device.
I would like to do a factory reset on this device.
wifi: enable wifi. If the signal is sufficient, I will
configure wpa_supplicant.
sound: silent
display: turn off auto rotate
turn down the brightness to the lowest setting
screen timeout: 1 minute
location: turn off gps
security: set screen unlock to none
turn off Scan device for security threats
turn off Verify at app installation
applications & turn on unknown sources
development: turn on android debugging
stay awake
turn off protect sdcard if it is enabled.
accounts&sync: turn off background data and auto-sync
Once the settings have been made and the device reconnected via usb, I need to attempt to access it via adb. If there is a security prompt, choose to always trust the host device.
Reporter | ||
Comment 1•10 years ago
|
||
mschifer, stephend, marcia: Can one of you handle this today? If so, please clear the other needinfos,
Thanks.
Flags: needinfo?(stephen.donner)
Flags: needinfo?(mschifer)
Flags: needinfo?(mozillamarcia.knous)
Assignee | ||
Comment 2•10 years ago
|
||
bc: Clearing stephen as he is out. I will look at it when I get in the office.
Flags: needinfo?(stephen.donner)
Assignee | ||
Updated•10 years ago
|
Flags: needinfo?(mschifer)
Flags: needinfo?(mozillamarcia.knous)
Reporter | ||
Comment 3•10 years ago
|
||
Marcia did a factory reset from the recovery and it appears to have helped not only with the job run time but also the throbber stop time has gone back to the previous level. Note that so far the local throbber stop time is being partially rejected due to variance. You'll need to change the selection to Include Rejects results. I'll keep an eye on it, but this is fixed.
Thank you Marcia!
Assignee: nobody → mozillamarcia.knous
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•10 years ago
|
||
Note the decrease in first run throbber stop time on 4/17
http://phonedash.mozilla.org/#/org.mozilla.fennec/throbberstop/local-twitter/rejected/2015-04-16/2015-04-23/notcached/errorbars/standarderror/notry
corresponds to an increased in second run throbber stop time
http://phonedash.mozilla.org/#/org.mozilla.fennec/throbberstop/local-twitter/rejected/2015-04-16/2015-04-23/cached/errorbars/standarderror/notry
and an explosion in noise for second run throbber start which was not improved by today's reset
http://phonedash.mozilla.org/#/org.mozilla.fennec/throbberstart/local-twitter/rejected/2015-04-16/2015-04-23/cached/errorbars/standarderror/notry
I think this device is dying. I'll try to swap in nexus-5-kot49h-3 and take this out of the pool for the next deployment.
Updated•3 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•