The altitude settings have gone crazy on all my created watches, and others FACER watch faces that download. I use TicWatch Pro 3 GPS. Altitude was correct for many months, but lately it’s been showing about 6,000 feet too high. (8621 vs 2700 ft) The altitude is correct on the altitude app on my watch.
I’ve removed and reinstalled Facer, deleted and recreated the altitude element on my faces. Restarted my watch, switched to a non-Facer face and back again.
Interestingly, my WatchMaker faces do not have this issue, nor does my watch if I check the altitude from the altimeter app, this is CLEARLY a FACER problem.
Jim, I just checked on my Fossil Carlyle HR and the barometric pressure is reading 0.6 InHg less than what the pressure is at the airport 20 miles from my house. It’s also reading the same on my Galaxy Watch 4. It sounds like it might be a bug with TicWatch in particular. I know when I had a TicWatch it was very finicky with Facer for some reason.
I just bought a Samsung Galaxy 4 Classic and my Facer watchfaces are STILL showing altitude about 6000 feet too high. I’m starting to think that Facer is not serious about this as I’ve tagged and emailed @Facer_Official multiple times with zero response.
I think when my Premium/Plus and Pro Creator expires I’ll not bother renewing any of them.
When I sync the watchface (also on watch 4) indoors it’s usually wrong but when I go outside for more than 5-10 minutes it gets the right altitude and then it stays updated.
Don’t know why.
I only guess, maybe outside could the watch get the altitude from GPS.
For inside (stairs count) there it would have to rely only on the barometric pressure sensor, which may need calibration time to time.
Calibration would not account for a 6,000 foot difference in altitude being reported, and this ONLY happens with Facer faces, every other face I have used gets the altitude right immediately.
Playing around with some math, I discovered that if I divide that altitude as reported by Facer by 3.14 (π) I get the correct altitude verified by standalone GPS.
I don’t think this Altitude error is just the Fault of Facer . This is the reading on my watch . It is from the Samsung Compass app which requires Location permission with the GPS on . I switched that on Two days ago . I have never had an App that gets it right . I know my Altitude because I live very close to a 100 foot Bench Mark . BTW we went Metric in the UK 1972 . If you want Accurate Altitude I would spend a bit more money and buy a Different Instrument . Google maps is a good source of reasonably accurate Height . But if you want LAT LNG that is a different story . That is spot on . It almoust seems like the Altitude error is deliberate .
.
.
You see it is that not simple . If you select Imperial as the user preference on your Watch you should get feet , if yo select Metric you should get Meters . So you see I say should . Now if you have set The User preference to Imperial and want meters you have to do some maths. I can not tell you what that is but if you Google it you will be given a factor for the conversion . I do that for speed . Despite the UK going Metric in 1862 we still use MPH and I like Degrees C for Temperature . Oh Well . If you get stuck Call back and I can show you something from my Laptop . Show us the Face you are trying to make a conversion on.
BTW In the screen grab I posted . The Samsung Compass App let’s you chose the units in the settings . Obviously I dependant from the Facer App / Watch settings .
