| Recurring |
one_organization, multiple_organization |
(a) The software failure incident related to Google's Battery Saver feature being turned on for users without their permission is an example of a similar incident happening again within the same organization. The article mentions that Google had previously used a kill switch feature in 2010 and 2011 to nuke apps it deemed malicious, indicating a history of such control mechanisms being employed by Google [75884].
(b) The incident with Google's Battery Saver feature affecting not only Google phones but also devices from other manufacturers like Essential Phone, Nokia 7 Plus, and OnePlus 6 shows that similar incidents can happen across multiple organizations or with their products and services [75884]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident described in the article is related to the design phase. Google's mistake in turning on the Battery Saver feature on Android devices was not a bug but a result of an internal experiment gone wrong. The incident occurred due to an error in the development process where an internal experiment to test battery saving features was mistakenly rolled out to more users than intended, causing the feature to turn on without users' permission [Article 75884].
(b) The article does not provide information about the software failure incident being related to the operation phase or misuse of the system. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident described in the article is within_system. Google conducted an internal experiment to test battery saving features, which was mistakenly rolled out to more users than intended, causing the Battery Saver feature to turn on automatically on Android phones [75884]. This incident originated from within the system as it was a result of Google's own actions and not due to external factors. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the article was due to non-human actions. Google conducted an internal experiment to test battery saving features, which was mistakenly rolled out to more users than intended, causing the Battery Saver feature to turn on automatically on Android phones [75884]. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident reported in the article is related to a hardware issue. Android users reported that their phones' Battery Saver feature mysteriously turned on, regardless of whether their batteries needed saving or not. This issue was caused by an internal experiment conducted by Google to test battery saving features, which was mistakenly rolled out to more users than intended [75884].
(b) The software failure incident is also related to a software issue. The problem with the Battery Saver feature being turned on without user permission was attributed to a bug in the Android P update. However, it was later clarified that it wasn't a bug but rather an internal experiment gone wrong, indicating a software-related failure [75884]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident described in the article is non-malicious. Google's mistake in turning on the Battery Saver feature on Android devices was attributed to an internal experiment gone wrong, not to any malicious intent. The incident was a result of Google conducting an internal experiment to test battery saving features, which was mistakenly rolled out to more users than intended [75884]. The article also mentions that there is no reason to believe that Google or Apple would intentionally do something devious, as it is in their best interests to keep owners happy and they are under scrutiny from researchers and power users [75884]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions, accidental_decisions |
(a) The software failure incident described in the article was due to poor decisions made by Google. Google conducted an internal experiment to test battery saving features, which was mistakenly rolled out to more users than intended, causing the Battery Saver feature to turn on automatically on Android devices [75884]. This incident highlights how a poor decision in conducting the experiment led to the unintended consequence of changing user settings without their permission. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
(a) The software failure incident in the article can be attributed to development incompetence. Google mistakenly rolled out an internal experiment to test battery saving features to more users than intended, causing the Battery Saver feature to turn on automatically on Android phones, affecting even devices not made by Google [75884].
(b) The incident can also be categorized as accidental, as it was mentioned that Google's mistake in rolling out the experiment to more users than intended was accidental, leading to the unexpected behavior of the Battery Saver feature on Android phones [75884]. |
| Duration |
temporary |
(a) The software failure incident described in the article was temporary. It was caused by Google conducting an internal experiment to test battery saving features, which was mistakenly rolled out to more users than intended. This resulted in the Battery Saver feature turning on by itself on Android phones, affecting users' devices. The incident was not a permanent failure but rather a temporary issue caused by a specific set of circumstances introduced by the experiment [75884]. |
| Behaviour |
other |
(a) crash: The software failure incident described in the article is not a crash where the system loses state and does not perform any of its intended functions. Instead, it involves the unintended activation of the Battery Saver feature on Android phones, which was a result of an internal experiment mistakenly rolled out to more users than intended [75884].
(b) omission: The incident does not involve the system omitting to perform its intended functions at an instance(s). It is more about an unintended change in user settings due to an internal experiment conducted by Google [75884].
(c) timing: The failure is not related to the system performing its intended functions correctly but too late or too early. It is more about an unexpected activation of the Battery Saver feature on Android phones, which was not intended by the users [75884].
(d) value: The software failure incident does not involve the system performing its intended functions incorrectly. It is more about an unintended change in user settings due to an internal experiment conducted by Google [75884].
(e) byzantine: The incident does not involve the system behaving erroneously with inconsistent responses and interactions. It is more about an unintended activation of the Battery Saver feature on Android phones, which was a result of an internal experiment mistakenly rolled out to more users than intended [75884].
(f) other: The behavior of the software failure incident can be categorized as an unintended change in user settings due to an internal experiment conducted by Google, which resulted in the activation of the Battery Saver feature on Android phones without users' permission [75884]. |