Your welcome!
Hope it helps others.
In my testing, I removed many variables, including using alternate Google and Samsung accounts, turning off wifi and all BT devices in my home, countless Factory resets, limited app installs, no migration of apps/data/settings during resets, and on/on. I gathered info here, on the Google Product forum and the Samsung Product forum. I learned a lot! Best guess that I'd make as of now is that the firmware underlying the OS somehow became corrupt.
That said, there's no accounting for all of the reports people shared with me about exchanges, repairs, and even changing to a different brand/model that didn't work - their issues persisted. For others, it started one day and a day/week/month later it just goes away. For me, an exchange was the ticket.
Hope it helps others.
In my testing, I removed many variables, including using alternate Google and Samsung accounts, turning off wifi and all BT devices in my home, countless Factory resets, limited app installs, no migration of apps/data/settings during resets, and on/on. I gathered info here, on the Google Product forum and the Samsung Product forum. I learned a lot! Best guess that I'd make as of now is that the firmware underlying the OS somehow became corrupt.
That said, there's no accounting for all of the reports people shared with me about exchanges, repairs, and even changing to a different brand/model that didn't work - their issues persisted. For others, it started one day and a day/week/month later it just goes away. For me, an exchange was the ticket.
Facebook
Twitter
Instagram