Conflicting Android beta reports: separating observations from verified bugs

Two separate Android beta reports have revealed different behaviors for the same breathing timer feature. The first report, from an unspecified device running a beta of Android 15, stated that the timer restarted after switching to another application. Meanwhile, a second report detailed a Pixel 7 device running the same Android 15 beta, which found that the timer resumed correctly after the app switch.

Another report highlighted an issue with a home-screen widget displaying a money-saved value. This value only matched the app's displayed amount after manually refreshing the widget, suggesting a potential bug in the app's widget functionality.

These observations, while user-reported, do not confirm the root cause of the issues, nor do they prove that these problems are widespread across all Android devices. To further investigate, a follow-up test plan has been proposed. For the breathing timer, testers are instructed to record the device model, Android version, exact steps taken, and the timer's displayed state both before and after returning to the app, after being inactive for a period of time.

This process should be replicated on the same device to identify any consistent patterns or discrepancies.

For the money-saved widget, testers are asked to use arbitrary input values. The app's displayed value and the widget's value are to be recorded, then checked again after reopening the app and after manually refreshing the widget. Crucially, these actions should be performed separately to accurately discern the impact of each action on the widget's displayed value.

Throughout this process, it is essential to maintain a clear distinction between three key statuses: 'Reported' refers to a tester's description of the issue; 'Reproduced' means that the same steps have been executed and the issue has been observed; 'Changed' indicates that an implementation fix has been applied. 'Verified' signifies that the original steps were retried on the updated build and the expected results were achieved.

At this stage, these notes only document the reports and suggest further tests. They do not claim that any fixes have been implemented or verified. The use of sample data in screenshots and reports is acceptable, but personal details, private journal entries, and sensitive information should be avoided.