7:15 AM PT – Swapped Kingston Class 4 4G sdcards for 00_23_76_96_cc_6f_nexus-one and c8_aa_21_ac_0c_b5_droid-pro after repeated failures checking for the device root.
19:00 PM PT – Both 00_23_76_96_cc_6f_nexus-one and c8_aa_21_ac_0c_b5_droid-pro showed an inability to properly detect and use the external sdcard. I cycled through most of the previously used sdcards attempting to find ones that worked. After checking almost all of the remaining older cards, I found one that worked in the droid-pro but could not find a card that would work with the nexus-one. In my attempt to get a working patch for bug 933842 – Add ability to specify test root in SUTAgent.ini, I realized that mozdevice’s devicemanager.getDeviceRoot() caches the reported value of the test root. Since the autophone workers survive the rebooting of a device, the cached test root value is reused until the device’s worker is restarted. This means that once an incorrect test root is detected, it will not be corrected by rebooting the device. I am testing an preliminary version of the patch for bug 933842 on the nexus one which forces the test root to /mnt/sdcard. I have resubmitted all builds from 2013-10-31 to now for both nexus ones and the droid pro. Hopefully the devices will be more reliable. It may also be the case that the older sdcards are not as unreliable as initially thought.
I also noticed that Autophone’s workers use devicemanager’s getDeviceRoot() to determine if a device is still responsive. Since the value is cached, this test is ineffective in determining if a device is still responding.
droid-pro-1 and nexus-one-2 sdcard change
nexus-one-2 (00_23_76_96_cc_6f_nexus-one) and droid-pro-1 (c8_aa_21_ac_0c_b5_droid-pro) appear to have difficulties with the new SanDisk Extreme Pro UHS-I. I have reverted back to the old Kingston class 4 4G cards on these devices. I have also discarded the older jobs which were pending so as to not confuse the graphs with a mixture of sdcards.
Any apparent regression from 2013-10-31 to 2013-11-01 for these two phones should be disregarded.
Kingston class 4 4G cards
I went through the older Kingston cards and performed a disk verification and repair using my Mac Book Pro’s disk utility. Those cards which could not be repaired have been removed from the active inventory. I will attempt to use the remaining cards in the devices which can not reliably run using the newer SanDisk cards. If a device appears to have issues with accessing the sdcard, I will attempt to swap in another and will move the offending card into an ‘unreliable’ category.
I received a number of phones from Haxxor Canada and am in the process of bringing them online to help partition devices between the s1s2, canvas SkiaGL and regression testing.
|Phone Type||DNS Name||Device Name||Notes|
|atrix-4g mb860||atrix-4g-1||40_fc_89_4c_95_3f_atrix-4g||cyanogen mod7 – Android 2.3.7, new SanDisk sdcard|
|htc-sensation-4g||htc-sensation-4g-1||18_87_96_a7_89_70_htc-sensation-4g||Android 2.3.4, new SanDisk sdcard|
|htc-sensation-4g||htc-sensation-4g-2||c0_3f_0e_ba_5f_34_htc-sensation-4g||Android 2.3.4, new SanDisk sdcard, Rooted but unable to reboot via SutAgent.|
|sony-experia||sony-experia-1||5c_b5_24_b6_7d_1f_sony-experia||Android 2.3.4, new SanDisk sdcard|
|droid||droid-1||a4_ed_4e_59_6c_b2_droid||Android 2.1, new SanDisk sdcard|
|droid-pro||droid-pro-4||98_4b_4a_13_01_84_droid-pro||Android 2.3.3, new SanDisk sdcard|
|nexus-one||nexus-one-3||90_21_55_09_87_95_nexus-one||cyanogen mod7 – Android 2.3.7, new SanDisk sdcard||samsung-gs2||samsung-gs2-4||14_7d_c5_af_c8_e3_samsung-gs2||Android 2.3.5|
2013-10-22 08:45 PT
Obtained new Micro SDHC cards (SanDisk Extreme Pro UHS-I cards) which match those in use for Panda testing and installed in the following phones which use external cards:
Any performance or reliability improvement in these phones in the next round of tests should be attributable to the new sdcards.
The shipment of phones from Haxxor Canada to Haxxor Virginia is being held up in due to an import clearance hold since Friday October 18. I’m not sure what is the cause for the delay but it may be due to a backlog caused by the U.S. Government “shutdown” this month. Hopefully the phones will be released soon.
07:30 AM PT
- samsung-gs3-2 battery drained, changed connection to a different USB port on the hub to recharge. Currently offline.
- droid-pro-1 found in powered off state, restarted
- nexus-s-2 hung on Mochitest-Canvas with proxy connection issue, restarted
10:28 AM PT
- samsung-gs3-1, samsung-gs3-2 powered back on after rest and battery recharging.
- droid-pro-1, nexus-s-2 hung on Mochitest-Canvas with proxy connection issue, restarted
6:13 PM PT
- samsung-gs3-2 hung on Mochitest-Canvas; required battery reset
- nexus-s-2 stuck on Mochitest-Canvas with proxy connection issue, restarted