1166752 - Autophone - device issues - 2015-05-20 nexus-5-kot49h-5

Status: RESOLVED FIXED

(Testing Graveyard :: Autophone, defect)

Description

[Bob Clary [:bc] (inactive)]

nexus-5-kot49h-5 stopped charging and appears to have fallen over and can't get up.

Marc, I think that nexus-5-kot49h-5 is no better at holding a charge than nexus-5-kot49h-4. I think the best course of action is to just swap nexus-5-kot49h-5 out and replace it with the old nexus-5-kot49h-4. One advantage is I will be able to use -4 to run the unit tests since it is rooted and has the sutagent installed.

I'll cut down on the tests/repositories that the nexus-5-kot49h-4 will test so hopefully it won't get into this discharged state quite as often.

Comment 1

[Marc Schifer [mschifer]]

I've replaced -4 back in to the rack and put -5 back into storage.  I have also swapped a couple of the USB cables around to see if I could get the nexus a better power source.  Let me know if it helps. There are two devices plugged directly into the back of the mini, we could swap those out for a couple of more powered USB hubs, maybe spreading the load a little more would help?

Comment 2

[Bob Clary [:bc] (inactive)]

Marc, Thanks! Do we have any more hubs available on hand?

Comment 3

[Bob Clary [:bc] (inactive)]

Marc, when restarting autophone this morning and attempting to put nexus-5-kot49h-4 back into production I realized it wasn't available by adb devices. Can you check on it?

Comment 4

[Marc Schifer [mschifer]]

-4 is the one stuck in rebooting and needs to be factory reset since I have not been able to figure out why it won't go past the initial shell.  I can either replace it with -6, which is ready to go, or do the reset or -4. In either case, they will need to have the superuser app re-installed and this was not working very well last time you tried.  

BTW: do we have any instructions on installing and configuring the SuperUser app? I can get the app, but it complains about not having the SU binary as well so I am not sure if I am doing it right or not.

Comment 5

[Bob Clary [:bc] (inactive)]

Normally Superuser is installed via clockworkmod recovery but I've been installing it remotely by installing the apk then manually copying the su binary to the device. I think we should just hold off on spending any more time on the nexus-5s except for basic maintenance.

Comment 6

[Bob Clary [:bc] (inactive)]

https://github.com/mozilla/autophone/commit/30dd2878c85b761f1fa2bc0753d7383f2e0b524c
https://github.com/mozilla/autophone/commit/1056a07e31664ada6dfe5b263050160648dcc463

Marc has swapped out one of the old hubs for a fully powered usb3/2 hub. We are still having issues with the nexus 5 devices in terms of booting to a spinner/boot animation; slow reboot but will put them under test until we can factory reset them all later today.

Comment 7

[Bob Clary [:bc] (inactive)]

We finally got the nexus-5-kot49h-{1,2,3,5} devices back on line. They initially came up attached to Mozilla-Guest network which caused problems with the remote tests. I cleared the problematic results and retested them and the result should be good now. nexus-s-4 also had a wifi problem where its wpa_supplicant.conf became corrupted. I fixed that and retested the affected builds.

snorp also ran try tests including all of the unittests. The nexus-s-[46] and nexus-5-kot49-2 could not run unittests. I tried nexus-5-kot49h-1 but it is also bad. nexus-5-kot49h-{3,5} can not run the unit tests due to rooting issues. We'll have to resolve this when I get to MV. Therefore I've disabled unittests including on try for nexus-s-[46] and nexus-5-kot49-2.

https://github.com/mozilla/autophone/commit/8f4ca86090cd82cd239decb5550f3b8e05e01604