Verizon Data works 4g LTE , no incoming text only outgoing , calls work .
After many many many calls to customer service, I have a SIM card in my Gemini with working data on the US Verizon network. The card had to be activated in a Verizon branded phone first, then moved to the Gemini. I had to manually set the Data Access Point Name to "vzwinternet" and the connection name to "Verizon". I would have thought the connection name was unimportant, but it seems to matter.
Problems I noted so far:
1. Data roaming had to be turned on for data to work when using many Verizon cell towers even though the MMC = 311 and MNC =480 of the towers. These are Verizon native towers, but data would not work unless I had roaming on.
2. There was a spot or two while drive 100+ miles where I lost coverage due to a tower using band 13 (as indicated by a Verizon branded phone). Band 13 is not supported by the Gemini.
3. With the CE edition of sailfish, I can not send or receive SMS messages. I can receive a phone call, but after the call completes, Sailfish complains that the SIM card is missing until I reboot the device. Sailfish can not originate calls (no service error) even though data is working.
I am also having trouble getting the Gemini/Sailfish to stop connecting to some rough network named "213423" with a corresponding MMC = 213 and MNC =423, which is strange because MMC = 213 is not for cell sites in the USA. When Gemini switches to this network, I need to turn airplane mode on and off again to get it to go back to Verizon.
When I have the stomach for Verizon tech support, I will call them about the roaming bug and the 213423 network, which seem to be a provisioning problem with my SIM/account.
------------------------------
Two Saturdays ago I stood by and watched a competent Verizon tech (asst mngr) do all that you mentioned and yet she failed to make my Gemini fully functional and compatible with Verizon.
Invariably everything tried would not take permanently. And what seemed to take would be lost after the Gem was restarted.
A huge failing with the Gemini's incompatibility with Verizon is the inability to add APNs and save with permanence edits to any of the Gem's listed Verizon APNs. Tweaked APN info either did not reappear among the list of installed Verizon APNs; or when it did once save and appear, the device remained unacceptably less than 100% functional. Furthermore, I did not like changing the various settings to accommodate my situational usage needs such as you mention.
So, fook'em.
All that capped off and ended too many weeks of failed efforts to make my Gem work well, without any dysfunction like those you describe, and that I, too, experienced with the Verizon SIM. Enough already. The fact remains that the device is designed and optimized for European users and unfortunately flawed for USA users on CDMA nets like Verizon.
That situational predicament Planet placed smartphone users like me in is disconcerting given the size of the US market for a device like the Gemini, even if it mostly garners niche interest from techie / Linux users over smartphone users like me.
Realizing and accepting that disappointing situation necessitated my porting four phone lines away from Verizon and end the trial-and-error processes I slgged through since receiving my Gem June 5th.
BTW, my deep, comparative research into this CDMA incompatibility issue (which I speculate Planet DID NOT DO SO THOROUGHLY AS ME) and learned understanding of GSM-enabled US cell carriers led me to choose MetroPCS / T-Mobile-Sprint (I live in the US mid-Atlantic region). Only switching cell carrier made my Gemini a fully functional 4G WiFi device, at last (and now costs me just $100 monthly - a welcomed upside I see as resulting compensation for nearly two months of aggravation caused by owning a Gemini).
Cheers!
P.S. Although I have stated often that I look forward to Gemini 2.0 - I shall not back it if Planet fails to choose a better, USA-cell marketplace accommodating chip set AND program the Android AND Sailfish OSs to be both 100% compatible and fully functional OUT OF THE BOX as a 4G-5G WiFi smartphone device on all but the smallest of US cell nets.
Ifanafi
------------------------------
I started out trying AT&T. That was even worse than Verizon out here in the Western Slope of Colorado. AT&T has a single 4G LTE tower in a two county area. All other towers are UMTS, in spite of the wonderful map their marking people have created that shows solid LTE coverage. Maybe I should bring this false advertising up with the US Commerce Department. Good luck to me on that. I think the broader problem is that US cellular providers suck. And a total failure of the US Government to require meaningful inter-operational regulations, portability, and standard compliance in exchange for the operators using our spectrum. While I would love to use T-Mobile, I live in a T-Mobile coverage hole. I had a really good experience with T-Mobile years ago, before they kicked me off there network for living in a roaming area. I don't blame them. It's was me who deceived them to get the service in the first place. Oh how I wish T-Mobile had service here.
As I mentioned previously, the Verizon problem appears to be provisioning, not the Gemini hardware, except for the lack of band 13/700MHz.
Regarding US band difficulty on the Gemini, and to Planet Computers' defense:
Every modern cellular modem has a baseband section, and an RF section, often in the same IC The baseband section is the same for all radio bands of operation since the underlying modulation is the same regardless of what radio band is being used. The RF section, with it's programmable I/Q modulator/demodulators can usually be tuned over most of the radio spectrum between 500 MHz and 6 GHz on the same IC. The front end Low Noise Amplifiers and RF driver amplifiers are also typically broadband as well. The trouble is with the interface between the amplifiers and the antenna:
1. A switchable RF filter is required for EACH band of operation,s both to clean up the transmitted signal before it hits the air, and to isolate the transmit and receive signal paths, which operate simultaneously, on different frequencies through a common antenna. (unlike WiFi where transmit and receive take turns on the same frequency). So even if the RF section can cover the entire spectrum of 500 MHz to 6 GHz, you still need to put a filter on the circuit board for EACH band. That ends up using a lot of space in the PCB.
2. The antenna inside the Gemini is small. It is very difficult to design an antenna of that size that is both efficient, and can cover a large number of RF bands. I have yet to see an OEM antenna from any manufacturer that covers ALL the bands in the USA with any respectable performance specifications. Especially with the addition of the old UHF TV 700 MHz band, which with it's lower frequency as compared to the other bands, makes the antenna larger. When the USA thinks it's special and it's going to go do thing's it's own way, this is what you get.
Take a look at the IoT radio modules from companies like Telit. There are always different modules for the US than for the rest of the world. They are pin compatible, but have different filters in the guts, and no antenna. They kick the antenna problem out to the user.