Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: The Real Bev Newsgroups: comp.mobile.android Subject: Re: Keepgo Data SIM Failure (Pixel 2) Date: Mon, 8 Jul 2024 23:52:10 -0700 Organization: None, as usual Lines: 121 Message-ID: References: <1fjr0g58yvjpn.dlg@v.nguard.lh> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 09 Jul 2024 08:52:13 +0200 (CEST) Injection-Info: dont-email.me; posting-host="e605ae7d57f3674330a75103de5785a9"; logging-data="1369248"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/H3n9Y2FV98oSKPyi6hcSB4z6b57ntLFA=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.12.1 Cancel-Lock: sha1:+1qjAzSDyvhnF4vCo2vF3YbVK/8= Content-Language: en-US In-Reply-To: Bytes: 7070 Keepgo Guy's latest suggestion -- remove and reinstall Google Voice. MIRACLE! THAT DID IT! I'm ashamed that I didn't think of that myself. My only excuse is that (a) that's a windows-like solution and (b) doing that generally wipes out all personalization, which is something I almost NEVER am willing to do. Still, I'm ashamed. On 7/8/24 10:20 PM, The Real Bev wrote: > On 7/8/24 8:25 PM, VanguardLH wrote: >> The Real Bev wrote: >> >>> Suddenly (well, maybe a few months ago -- I rarely use it) I am no >>> longer able to contact google voice via the SIM. It contacts websites >>> fine, but doesn't connect to google voice at all. The Keepgo people are >>> responsive and I have followed their instructions regarding the APN, and >>> they haven't given up yet, but to no avail. >>> >>> I had thought that I used it to make a google voice phone call a few >>> days ago, but it went through our home (or other) wifi rather than the >>> SIM. Latest google voice update was (I think) June 24 2024. I know it >>> WAS working earlier in the year because I made calls from my car when >>> there was no wifi hotspot nearby. >>> >>> Has google voice made some change since March or April that might have >>> created connection problems? The service was perfectly good at a >>> reasonable price ($30 for 3GB plus $3.00 for another 1MB to keep the >>> unused data rolling over) and I've only used 500MB in a year and would >>> like to keep it. >> >> Never used the cellular provider (KeepGo) you are talking about. >> According to their web site, they only offer cellular data service. >> However, don't you have to grant use of a device in your GV account, >> like under "My Devices" or "Linked numbers"? I'd check there to ensure >> your GV account is configured to work with your device. > > It is and was. Something happened. > >> I have an old phone still back on Android 8.0.0. No chance to upgrade >> to later Android versions since LG, my phone maker, discontinued the V20 >> phone back in 2019, and then LG left the smart phone market in 2021. My >> phone got orphaned by LG. The GV app on my phone is version >> 2024.06.17.645382423 (June 17, 2024). It still does get updated >> occasionally, and each time I'm nuisanced with a new notification about >> how GV will be used to [asked to] make calls. The Play Store web page >> says the last update was July 8, 2024). I just checked the Play Store >> app on my phone, and it reports no updates, so I'm not [yet] offered the >> July update. > > I see the July 8 date at the website, but mine doesn't need updating > yet. Not my turn, I guess. >> >> The vast majority of time when I use the GV app on my Android phone is >> at home, and that is using the wifi connection to the cable modem, so >> I'm not much using GV via cellular data. > > Likewise, so I didn't notice the problem until recently. Suddenly I > feel like most people probably feel when they discover they left their > phone at home :-( > >> When using wifi for an >> Internet connection to reach the GV service, KeepGo nor any SIM is >> involved. You said GV is usable via wifi, but not via cellular data >> using KeepGo. When using a wifi connection to GV, any quota >> restrictions for your KeepGo service do not apply. If GV still works >> via wifi to Internet, maybe you need to log into your KeepGo account to >> check you still have some quota. > > They say I have roughly what I say I have -- 2.5GB remaining; > Expieration is August 4, but I'll buy $3 worth of data (1MB) to keep it > rolling over. > >> You said you can still reach web sites using cellular data with the >> KeepGo SIM which indicates you haven't hit a quota ceiling. However, >> could be KeepGo has a problem getting to GV. When working with KeepGo >> techs, did they even test if GV was reachable by them? > > They can reach it. They say I was attempting to connect to a wrong APN, > but that made no sense because my setting used the correct one. I made > a new APN with the settings they noted. Same problem. SOMETHING is > missing between Keepgo and google voice. > >> Could be the >> problem is on their end, not yours. KeepGo doesn't operate their own >> network. In the USA, they mostly use the AT&T, T-Mobile, and Verizon >> networks (https://www.keepgo.com/pages/list-of-providers-by-ciountry). > > Their home address is in Spain, but they say that doesn't matter. I sent > them screenshots of my settings, and they didn't say anything was incorrect. > >> Unclear is if you are using the GV app on your phone, > > The app. > >> or using a web >> browser (and which one) to connect to voice.google.com. Google has a >> nasty habit of requiring some non-ratified or proprietary functions in >> their web pages requiring you use their Chrome web browser, or variant. >> On my home PC, I use Firefox to connect to GV. On my Android phone, I >> use their GV app, but my GV app version is 3 weeks older than what the >> Play Store app page says. > > They suggested using a different browser (Opera) to connect with GV. > That made no sense at the time, but since I connect through firefox and > chrome on my computer, perhaps the same thing can be done with Android. > > I generally use the android default browser (I assume it's chrome) > because firefox is slower. I'll try going through browsers rather than > the app... Still makes no sense unless google somehow screwed around > with the app. > > OK, I went through chrome and it worked fine. Hard to see and use, but > at least it works for outgoing calls. For incoming calls, I'm asked to > press 1 to accept the call, but it doesn't seem to recognize the press. > Still, progress... -- Cheers, Bev FAILURE IS NOT AN OPTION. It comes bundled with the software.