jimlarkey

"...earth stations in the US are allowed...", not the same as enabled. Check the fine print before you buy. Response from European GNSS Service Centre (GSC) regarding the LG-V30 (above): "According to Waiver of Part 25 Licensing Requirements for Receive-Only Earth Stations Operating with the Galileo Radionavigation-Satellite Service of FCC and Released on 16th November 2018: …to permit non-Federal earth stations within the United States to operate with certain signals from the Galileo GNSS without an earth station license or a Galileo GNSS market access grant. That means that earth stations in the US are allowed to operate with Galileo E1 signal (1559-1591 MHz band) and Galileo E5 signal (1164-1219 MHz). The chipset makers were all on board to activate Galileo as soon as the FCC waiver entered into force. Therefore, we regret to inform you that we have no information if LG has activated Galileo in its devices. In the meantime, we recommend you to contact directly this manufacturer asking if Galileo signals are or will be enabled in their devices."

Another thing to consider before buying is whether the phone manf'r supports the constellation in your market area. The chipset on my LG=V30 cellphone is Galileo capable, but LG has not enabled it in the US market. From LG: "According to our resources, the LG V30 H932 phone is designed exclusively with A-GPS technology for enhanced location accuracy. While the chipset is said to be compatible with Galileo GNSS for Europe, this is yet to be supported by the LG V30 H932 phone model as it's made for the U.S. market. Other V30 models or counterparts from Europe may support this technology based on their location."

Just an update on the OP's old Google Earth Pro not linking in Mapsource, today...the RegServer fix above will not solve today's problem. "This worked fine until the latest release 7.3.3. Now it tells me that Google Earth Pro is not installed and I need to go to the Google website for download. I reinstalled version 7.3.2 and the connection works fine again." https://support.google.com/earth/thread/45536001 Yes, you'll need to stick with v7.3.2 or reinstall if you want Mapsource to link to View in Google Earth.

Things could be worse than your handheld. "GPS ROLLOVER GONE WRONG The April 6 GPS Week Number Rollover was supposed to pass without a hitch, with plenty of notice that updates might be required for legacy receivers. Instead, several systems crashed. In China, as many as 15 Boeing 777s and 787s were grounded pending a GPS update (the receivers gave the date as August 22, 1999.) In New York City, part of the wireless grid faulted, cutting information feeds to the NYPD (license plate cameras) and remote worksite communications. In Australia, weather balloons were grounded. In the United States, NOAA autonomous monitoring stations went offline. Fixes for all these systems are underway." Courtesy May issue GPS World

Yes, had the problem with Mapinstaller 4.2 (latest), rolled back to 4.0.4 same problem. At some point Garmin changed their policy on supporting 3rd-party maps. I don't know what version of Mapinstall that occurred. Not gonna spend the time rolling back again and again until I find it. No problem with OSMs....only GPSFileDepot maps. Mapsource install works on GPSFileDepot.

See orig post: " On my end I'm running the latest version of Win 10 (10.0.17763), installing on a Garmin OR-700 SW v4.40, using latest Mapinstall v4.2.0, last Mapsource v6.16.2" Problems.

Yeah, Mapsource is the way to go. The above poor-detail image was installed with a rolled-back version of Mapinstall: v4.0.4 (4.2.0 is current), as well as rolled back version of Basecamp: 4.6.2 (4.7 is current) The problem is which if any of the versions below did Garmin change their policy of crippling the detail? MapInstall 395.exe MapInstall 400.exe MapInstall 401.exe MapInstall 403.exe MapInstall 404.exe (not) MapInstall 420.exe (not) MapInstall 3101.exe MapInstall 3102.exe MapInstall 3103.exe MapInstall 3111.exe MapInstall 3114.exe MapInstall 3115.exe MapInstall 3116.exe MapInstall 3121.exe MapInstall 3132.exe MapInstall 3135.exe MapInstall 3142.exe MapInstall 3144.exe MapInstall 3150.exe

Thanks StefandD. I heard reports that Garmin disabled, didn't know that they crippled. Yep, have no problem with OSMs, but it's the 3rd party maps on GPSFileDepot. Can find cotopo11 under Colorado. I did roll back to v4.6.2, and I did rollback Mapinstall to 4.0.4....image of compiled map comparison below. Compiled file sizes tell the story: cotopo11_Mapinstall 185 MB (194,883,584 bytes) cotopo11_Mapsource 784 KB (802,816 bytes) Thanks again, and all praise be to Mapsource.

Anyone else have a problem with the latest version of Garmin's MapInstall, crippling and corrupting the compiled img file on the target device (uSD card)? I installed some OSM topo routable maps, and deleted some existing 3rd party maps from GPSFileDepot in the process. Tried to reinstall the 3rd-party GPSFileDepot maps with Mapinstall, and the compiled maps lacked detail, and were very crude....no topo line, missing highways, crude shaped reservoirs, etc. The compiling time was very short, and the resulting map img files seemed about a 1/3 size of what they were. 3rd party maps were: cotopo11 My Trails (layer) us_p_nw (planimetric NW) Even Garmin's (legacy) TOPO US 2008 and Metroguide v8 were crippled and lacked/missing detail. Solution: used compiler/installer in last version of Mapsource, v6.16.2. All the maps above installed including the OSMs, as separate compiled img files....and they all have the full detail levels. Thanks be to Mapsource again, but I wonder if Garmin changed the code in the MapInstall proggie to cripple the detail level of the compiled img file of the target 3rd-party maps? Has this been discussed previously? Anyone else encounter this? On my end I'm running the latest version of Win 10 (10.0.17763), installing on a Garmin OR-700 SW v4.40, using latest Mapinstall v4.2.0, last Mapsource v6.16.2

phlemicus: strange again that the rollover would have that effect. Garmin's published statement: " the positioning accuracy will not be affected. The device will continue to deliver the same positioning performance as before the rollover. " Garmin GPS Week Number Rollover Statement

Agree that it is likely chip-based, but still strange that Garmin doesn't oversee or overlooks spec on rollover. As I mention above, my Garmin GPS V (ca. 2001) is OK, but Nuvi 550 (ca.2008) fails.

alandb says " re there any nuvi 5x0 users here, and if so are the devices still working with a correct date now that the date rollover has passed?." I've got an old Nuvi 255W (ca. Mar 2008) which fired up with correct time/date/year. Strange that the 550 (ca. Jul 2008) does not.

Garmin GPS V (circa 2001) OK...for now. As Spirent’s Guy Buesnel writes, that means “the impact won’t necessarily be felt on rollover day itself. In fact, it’s much more likely that an affected receiver won’t start outputting erroneous data until long after the 6 April 2019.”

You don't even need an cell phone app, the night vision goggles on SAR helicopters "sees" the light from the screen of the cell phone very easily. " Cell phones can also be used as a signaling device during the night. Should you find yourself lost and without a flashlight, use your lighted cell phone screen by turning it towards any ground search and rescue or helicopters you hear. " https://www.sbsheriff.org/sheriffs-search-and-rescue-team-rescue-lost-hiker/

+1 on the http://www.gmaptool.eu/en/content/usa-osm-topo-routable maps. I found that installing the topo-routable OSMs on my Oregon 700 corrupted the display of other maps, such as the OSM-Bike map, cotopo11, TOPO 2008, etc, but the topo-routable OSMs are so feature rich that I uninstalled all the other maps. Further, the topo-routable OSMs are up to date. They show the road layout of a subdivision completed last year. Great maps. Thanks to the TheMolesFamily

Some resource material: http://www.laptopgpsworld.com/4666-gpsmap-60csx-chipsets

I'm still waiting for this....

Unfortunate that Garmin does not put out solid handheld GPSrs like they formerly did.

Life is not simple...."not constant current" like one would like to assume. Each manufacturer has their own charging algorithm. I could post the MAHA, or LiitoKala envelopes, which all very in current profiles, and different from each other. "The MH-C9000 uses a combination of Negative Delta V, Zero Delta V, Peak Voltage, time and temperature to determine the end-of-charge. In addition, proprietary algorithms are used." Cheers.

I don't have a Garmin 64 but I did log the charging current in my OR700, which might have a similar charging envelope. Power source was an Anker PowerPort+ 1 Quick Charge 3.0 Wall Charger. The full charging time was about 4 hours, with 1-second sampling, so displaying the full graph would be difficult to display w/o zoom feature. I did notice 3 distinct patterns in the 4-hour long charge, bringing the Eneloop HR6's from 1/2 discharge to full charge. A sample of each of the 3 distinct charge envelopes is shown below. The charging algorithm is not as simple as you might think, or want it to be. I've noticed this in other chargers as well, so it's not a Garmin thing.

USB 1.0/2.0 is good for up to 500mA. USB 3.0 good for 900mA. I've got the same eneloop hack as dbrents on my OR700....360 mA charging.

No internal battery....not a powerbank. But...if you load a pre-charged high energy density cell like an 18650, it will function as a powerbank.

...." that I can connect to a power bank or my car's usb ports "....

You can charge your Eneloops directly.....

My method might not exactly align with your thoughts exactly, but the charger I reference will charge eneloops directly. http://www.candlepowerforums.com/vb/showthread.php?415403-Test-Review-of-LiitoKala-Lii-100 I use Eneloops in my OR700 and charge them in situ....I don't remove them. I charge 18650 Li-ions in the Li-100 charger, and charge the Eneloops from that. I use other devices that are 18650-based, so I'm a real fan of and commited to 18650s. You may not be. You can of course charge your Eneloops directly in the LiitoKala charger and load them into your GPSr, or other Ni-MH based devices. I use the single cell Lii-100 because of it's light weight in a backpack. There is a 4-cell unit, as well as a 2-cell unit (below). http://www.candlepowerforums.com/vb/showthread.php?425279-Test-review-of-Charger-LiitoKala-Lii-202