View Single Post
Old 05-20-2019, 08:53 AM   #21
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,646
Karma: 204624552
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by j.p.s View Post
K2 was Sprint. reports of K2 connectivity loss started showing up here some time ago.
Only the early US-only version of the K2 was Sprint. The later international versions of the K2 (2009-ish) switched to ATT. I was one of the ones reporting connectivity loss (but only after a factory reset) back in 2017, but Amazon corrected whatever the problem was and I was eventually able to re-register and connect. I'd have to dig it out of the Gig-Bag-of-Retired-Gizmos-that-Lives-in-the-Bottom-of-the-Closet (and see if it will still hold a charge) to see if it can still connect.

But even back then (2007) there were many reports of DX(G)s not being able to register/connect even after the problem with the K2s was resolved.

Last edited by DiapDealer; 05-20-2019 at 09:02 AM.
DiapDealer is online now   Reply With Quote