I've got the AT&T version of the S3, and it's stock, unrooted, with the most recent updates (version 4.1.1).
This morning I noticed a bug with the stock calculator that has not happened before. If I type five digits, the fifth digit is placed right after the first digit. Example: If type the digits 1, 2, 3, 4, and 5 (in that order), the display will show
instead of "12,345".
What appears to be happening is that when I type the fourth digit, the calcutor inserts a comma separator. When it inserts the separator, the cursor moves in front (to the left) of the separator, so that when I type the fifth digit, it gets placed right before (to the left of) the separator instead of at the end (right) of the number.
I can confirm this by correcting the cursor placement and typing additional numbers. The cursor is moved when another comma separator is placed.
Has anyone else seen this? As noted, at one point the calculator worked fine.
I've tried the following in order to resolve, but none of them have worked.
Edit: Resolved, see post below.
This morning I noticed a bug with the stock calculator that has not happened before. If I type five digits, the fifth digit is placed right after the first digit. Example: If type the digits 1, 2, 3, 4, and 5 (in that order), the display will show
15,234
instead of "12,345".
What appears to be happening is that when I type the fourth digit, the calcutor inserts a comma separator. When it inserts the separator, the cursor moves in front (to the left) of the separator, so that when I type the fifth digit, it gets placed right before (to the left of) the separator instead of at the end (right) of the number.
I can confirm this by correcting the cursor placement and typing additional numbers. The cursor is moved when another comma separator is placed.
Has anyone else seen this? As noted, at one point the calculator worked fine.
I've tried the following in order to resolve, but none of them have worked.
- Clear the calculator app's cache and data,
- Reboot the phone, and
- Battery pull
Edit: Resolved, see post below.
