04-12-2009 11:41 PM
So I get reasonably accurate altitude from a Bluetooth puck via the same location API , so really there is something wrong with the BB hardware.. it cannot provide accurate altitude while other GPS devices can?
04-13-2009 01:11 AM
The altitude values I get here are within 15-20 metres but the wrong sign however other people have reported much larger discrepancies, for example one user of my application gets -500 ft at sea level in the UK. I think the BB GPS hardware is just not capable of providing worthwhile altitude data.. I have 3 other GPS devices all of which provide correct values.
06-15-2009 07:24 AM - edited 06-15-2009 07:42 AM
In contrast to what I have earlier posted (about WGS84) I have encountert today a very strange behaviour. A Storm User have used my GPSLogger application on a Skydive jump - and the logged data is really really strange! - Since when he lifted off with the plane the recorded
is decreasing constantly - it starts at - 39m (which is a possible value in WGS84) and then it goes down to -4719.0!!!
In WGS84 you could have negative values at least down to minus 100... but for sure not smaller then this... so what this storm have recorded is way OFF...
The Number of satalites is also recorded - ans it's always above 9... so right here and right now I would like to say, that the data that I receive from the javax.microedition.location.QualifiedCoordinates is not correct - I have to multiplicate it with -1 to get the correct values... I will investigate the NMEA sentences a bit more in detail, if I can find a reason for this.
06-15-2009 09:31 AM
Just as update - I have now additionally logged the MNEA sentence...
and already there I get on my Storm always a negative values for the altitude (alt is the 10'th value in the $GPGGA sentence -> see http://calvin.yeung.us/NMEA_sentences.htm)... So my assumtion is, that something in the lower level get's wrong...
06-15-2009 10:03 AM
06-16-2009 04:00 PM
12-01-2009 02:33 PM
I can understand that it may take really long time to fix the problem. But it would be helpful if you could characterize the problem technically bit more from your point of view. I am looking for some sort of work around that is likely to work on reasonable of the cases.
Our customers want to switch to Iphone/android early next year if this is not resolved. Anything to reduce the intensity of this option will be really appreciated.