I disagree that the native navigation app correctly accounts for elevation gains as some have stated. My experience driving in California up and down by thousands of feet has led me to this conclusion.
For example, driving south to LA over the 4000-foot Tejon pass on the I-5 north of LA, starting in the Central Valley at the grapevine the native app may have one charging stop in LA on the route south to Orange County. As I climb the hill, the native app announces that it may not be possible to reach the destination and that additional charging stops may be necessary. Then a few minutes later the native app will add a charging stop. Then as more climbing occurs this sequence can repeat as other charging stops are added. I just ignore this because after the summit the native app will announce that a charging stop is no longer needed and then it removes the added charging stops as we drive downhill.
As a test, I set the native nav to go from sea level here in Santa Cruz to Northstar ski area in Tahoe, at 6300 feet and 260 miles away. Starting with 23% SOC, ABRP says I will need 2 charging stops, one in San Jose from 8% to 65%, and then a second in Sacramento from 10% to 76% to arrive at the ski area with 10%.
The native app, also starting from Santa Cruz at 23% SOC, says I need only one charging stop in Fremont, 14 miles after the first ABRP charging stop. At Fremont we charge from 10% to 67% according to the native app, to arrive at the ski area with 7% SOC.
So the native app thinks we can drive the 207 miles from Fremont to Tahoe and up over the 7000 ft Donner pass without charging again. No way.
I have found that ABRP is fairly accurate when there is no wind or heavy rain. ABRP accounts for large elevation gains but the native app seems to think that California is flat.
![Image]()
![Image]()
![Image]()
![Image]()
![Image]()
![Image]()
For example, driving south to LA over the 4000-foot Tejon pass on the I-5 north of LA, starting in the Central Valley at the grapevine the native app may have one charging stop in LA on the route south to Orange County. As I climb the hill, the native app announces that it may not be possible to reach the destination and that additional charging stops may be necessary. Then a few minutes later the native app will add a charging stop. Then as more climbing occurs this sequence can repeat as other charging stops are added. I just ignore this because after the summit the native app will announce that a charging stop is no longer needed and then it removes the added charging stops as we drive downhill.
As a test, I set the native nav to go from sea level here in Santa Cruz to Northstar ski area in Tahoe, at 6300 feet and 260 miles away. Starting with 23% SOC, ABRP says I will need 2 charging stops, one in San Jose from 8% to 65%, and then a second in Sacramento from 10% to 76% to arrive at the ski area with 10%.
The native app, also starting from Santa Cruz at 23% SOC, says I need only one charging stop in Fremont, 14 miles after the first ABRP charging stop. At Fremont we charge from 10% to 67% according to the native app, to arrive at the ski area with 7% SOC.
So the native app thinks we can drive the 207 miles from Fremont to Tahoe and up over the 7000 ft Donner pass without charging again. No way.
I have found that ABRP is fairly accurate when there is no wind or heavy rain. ABRP accounts for large elevation gains but the native app seems to think that California is flat.
