I use GPS TEST app to test the gps functionality of my Note 5 and it seems that the gps will jump most of the time from 6 to 12 meters of accuracy when i'm outdoors and very rarely hit 4 meters or 3, no matter how many sattelites are in use (usually more than 10 and most of the time even 20+, which is great). it feels like a software calibration thing - my older devices would show 3-4 meters consistently when the reception was good ; I also noticed that my movement in Waze seems to update more slowly when compared to other devices.
How's the situation with yours?
didn't realize it could go that low 4m accuracy. how does it impact your usage of GPS when u get only 6m-12m accuracy?
Civilian gps devices are restricted to 3m. Military gps devices can get even more precise. Back to your question - It doesn't seem to effect it for driving purposes, but if I use apps such as Runtastic, it feels a bit off track.
So... How's the accuracy of your Note 5's? Did you manage to get a constant 3-4 meters?
Related
I am looking for some feedback on the GPS built into the new AT&T Tilt.
What is the accuracy of the GPS?
What is the sensitivity of the radio? (does it loose signal when you get in your car? in heavily wooded areas?)
How long does it take to obtain GPS Satellite Signal? (15 seconds? 30 seconds? 2 minutes?)
How much battery does it suck down?
Can it work with multiple programs at the same time? (Windows Live and another program at the same time?)
Can't really comment on accuracy, but it has me plotted on the correct roads on Google Maps and MS Live Search.
GPS reception is fine in the car, although initial satellite lockings seems faster when I put the phone on the dash. After that, I can pretty much put the phone anywhere near the drivers seat.
Takes a minute to a couple minutes for me to get a fix.
Its sucks batteries fast. Slightly faster then the trickle charger is charging the phone. So on a long drive, I imagine you will kill the battery on the Tilt using the GPS.
Don't know about the last question.
Braingears said:
I am looking for some feedback on the GPS built into the new AT&T Tilt.
What is the accuracy of the GPS? :iterally its pinpointed me w/in 5 ft
What is the sensitivity of the radio? (does it loose signal when you get in your car? in heavily wooded areas?) In the car its fine, dont have woods here in miami, but in the everglades it works just fine.
How long does it take to obtain GPS Satellite Signal? (15 seconds? 30 seconds? 2 minutes?) approx 10-15 s
How much battery does it suck down? Dont know, I dont have it on for a long time
Can it work with multiple programs at the same time? (Windows Live and another program at the same time?)
Click to expand...
Click to collapse
Havent tried that yet, meaning using google maps & windows live?
I've only had it working for a short time, but based on what i've read its fairly accurate (someone got it within 15', mine was within 30' but that was google maps and i dont think it does off-road)
I established the connection on my porch (so i could use my wifi) and it followed me inside the house. 9 satellites outside, 6 in my chair. its a small house, but still nearly completely obstructed due to rain clouds and being indoors
If you use a program like GPSTest or GPSViewer to establish the connection first, they go very quickly. otherwise it may run into some problems connecting due to the timeout settings.
battery power no idea...
As mentioned earlier, i try a light weight program to establish the initial connection and the actual program to use it. from what i've seen you can see two but not sure how well it'll work n the end.
hey i got my tilt, I really don't know how things works, I mean I installed live search on it, but you know I can't get the current GPS postion, how does this thing work? anyone? can you guys tell us the steps for those of who are new to this whole GPS thing, thanks
redpoint73 said:
Its sucks batteries fast. Slightly faster then the trickle charger is charging the phone. So on a long drive, I imagine you will kill the battery on the Tilt using the GPS.
Click to expand...
Click to collapse
I noticed this too.
Is there a way to fix this?
It is very annoying.
With a car charger I should be able to at least keep the battery at the same level.
(PS: I am using a car-to-USB adapter and the USB/Sync cable that came with the tilt)
Back when I was using the att flash, I'd need to use a program to jumpstart gps. It'd take about 2 minutes. Afterwards, I could use google maps without issue. But if I drove around, I'd constantly be losing the gps and need to hit retry.
Then I flashed to htc. Google maps always picked up the lock in about 10 seconds. I'd still lose it if I drove around.
But then a few days ago, google maps stopped picking up gps. Even using other programs, I'd run it for over 10 minutes without getting a lock. Haven't gotten gps working at all in the past few days. Not sure what's going on. Hopefulyl a future firmware will fix this. Not going to bother with it for the time being. Being able to use google maps is really enough. gps is pretty silly to me.
Braingears said:
I am looking for some feedback on the GPS built into the new AT&T Tilt.
What is the accuracy of the GPS?
What is the sensitivity of the radio? (does it loose signal when you get in your car? in heavily wooded areas?)
How long does it take to obtain GPS Satellite Signal? (15 seconds? 30 seconds? 2 minutes?)
How much battery does it suck down?
Can it work with multiple programs at the same time? (Windows Live and another program at the same time?)
Click to expand...
Click to collapse
Accuracy -- I can't speak as to "within x meters", but I can tell you that when using it with mapping software, the location fix is right on the money as to where it shows me being in the car.
Length of time to obtain a signal -- after the initial "fix", I can open my mapping software and in the length of time it takes to select my destination, it has already paired with the GPS chip.
Battery Life -- I keep my Tilt on the car charger when using GPS -- at least, I did until a few days ago. I forgot to plug it in to the cigarette lighter and the battery was dead running the GPS constantly in 5 hours.
Multiple apps at once -- Can't comment on that one.
When I use telenav , most of the time it is accurate close to about 15 feet.
Hello guys
I'm using the igo v8.3.2.64873 with the stock rom on my TP. Somehow the gps speedometer in the igo shows a speed which is about 7 km/h lower than the actual speed of my car.
is there any option to fix this ?
Thank you
IGO
And what are you waiting for m8 ?
The speedometer is reliying to the satellites and the gps system is not error proof. Your position is not correct to the centimeter hence your speed is no one hundred percent accurate either.
Beside, the speedometer on your car is not a precision tool either so it may be not very accurate itself.
7 kph seems very few.
eurorpeen said:
And what are you waiting for m8 ?
The speedometer is reliying to the satellites and the gps system is not error proof. Your position is not correct to the centimeter hence your speed is no one hundred percent accurate either.
Beside, the speedometer on your car is not a precision tool either so it may be not very accurate itself.
7 kph seems very few.
Click to expand...
Click to collapse
ok thanks anyway
krot84 said:
ok thanks anyway
Click to expand...
Click to collapse
Just FYI-
The speedometer on a car is usually ~5-10% optimistic, if we are talking at 7k"m/h from a 100km/h speed than that is quite within reason.
ok, man, but it sucks to see the difference between them both
Anyone using USA maps notice the ETA can be way off? Its not as noticable for shorter trips, but it is very noticeable for long trips.
I'm using the Q2 2008 NAVTEQ maps.
I did a 330mi trip which should take about 5 hours (according to Garmin, Google Maps, etc), but this version of iG0 says it'll take 6+ hours. As I drive the time will keep getting more accurate and by the time I'm 4 hours into the drive it'll be within about 20 minutes accurate while Garmin would be accurate the whole trip.
Do you think this is a map issue or an iGo issue? I had 8.0 and 8.3.1 and they exhibit the same behavior, but they all used the same maps.
So, I took my Nexus One for a spin using Google Turn-By-Turn navigation and it was like a 25 minute drive and when I got home, the phone was really hot, to the point where i was afraid this thing may be close to being fried on the inside. The touch screen wasn't working properly (not responding to touch and being very inaccurate than normal). I left it on the desk and after 5 minutes it cooled down again and was fine.
What the heck is wrong? is it cause I kept it on the dash board against the dials, that area was kind of warm but nothing to heat up the phone that much, should I be using a cradle or something?
Its a fully stock Nexus with 2.2.1 FRG83D, not rooted and no other apps running. Same thing happened with the free program MapDroyd, so it isn't Google Navigation only issue either.
I don't use GPS much, but when I first got it, I did and it was fine. After about 9 months though its started getting pretty warm, within minutes of using 3g, roughly 38degrees celcius (about 100 fahrenheit), but apparently it's been tested and works fine up to 57 celcius (134 fahrenheit) or something like that.
it's not the gps .. it's the turn by turn navi.. it uses massive amounts of CPU that is what heats up
It is a number of factors, including the previously stated turn by turn navi. You also have the screen on permanently, plus at least where i live, anything in a car not in an air conditioning stream is going to heat up a lot.
I suggest getting a setcpu widget or some other temperature monitoring widget. I also set my cpu to underclock when it gets above 48 degrees C.
Heavy CPU usage, GPS probably generates some amount of heat, but mainly it also adds to the battery draw which adds heat. Screen is on, and you're possibly also downloading quite a lot of data unless your maps are entirely offline.
Also, your phone might be sitting in the sunlight, or in the winter might have the vents blowing over it.
So just the GPS? Not really. Run GPSTest sitting on your desk. You'll see significant battery usage (probably adds 120mAh to what it'd normally use) but it won't get hot.
Yeah, turn by turn navigation does seem to heat it up a lot, even when caching the map offline entirely on a Wifi network beforehand. My phone isn't rooted, but maybe I'll root it and use setCPU thanks.
Will actually heat up more if plugged in. Although mine never gets past 115 or so and this is with GPS and music playing.
Not Sent from a pc/mac
I'm now 3 days into having a refurbished UB2 and learning what it can and cannot do, its limits, before I rely on it.
I have a usual bike loop of about 70 miles with 6000ft of ascent and I do it in about 5hr30m typically. I thought I'd try the UB2 "standalone" off from BT, left the mobile at home, to see what happened.
The UB2 was losing 25% of its battery an hour meaning it cannot do more than 4 hours. It kept connecting / disconnecting. It had no clue about my actual calories, I was using Google Fit and it was giving the same dumb 500Cals/hour even when going up a steep hill, it seemed to only know about speed even though GPS obviously knows you are going up or down hill, so it was showing me burning calories quickly on a downhill and slowly on an uphill when the truth is the opposite. If all it is going to do use is elapsed time, I can do that math easily.
As I had no mobile with me, the problem was the UB2 was my emergency phone so I took it off my wrist, when I got to 44% of power left at around 2 hours in to ensure it was not flat, connected it to power (I have a USB power socket on my bike via front dynohub) to top it up, and then Google Fit determined the act of connecting to power must equal I was no longer biking when not true so it stopped the timer.
I have previously tried Google Fit on a mobile and it drained the mobile battery pretty fast too.
The heartrate was unreliable, I was getting between 56 and 133. It seems reliable when stationary but not when moving, so meaning its not going to accurately tell you much of value.
The GPS got stuck and it stopped recording distance. I was not sure if this was me trying LG's fitness app (which I cannot uninstall) vs Google Fit, I was wondering these competed for GPS and the watch got confused?
The radio frequencies, across 2g 3g 4g were in general worse coverage than a mobile, I was getting no signal on UB2 in places I'd get a signal with a mobile.
Probably this is a better device for walker/runners who go out for less time, more in urban situations near stronger radio signals.
I have now flashed to AW2 and will try it again, see if its less dumb than AW1.5. I think I'm going to totally give up Google Fit, its laughably less than useless given its wildly wrong and a battery drain, and just go away from mobile and see how long it lasts.
I'm not sure what is the point of LTE and a stiff band for antennae, if it holds a weak signal, nor of it being a fitness device if using it more than a 4 hours makes it go flat, nor what is the point of the heartrate monitor which is so wildly inaccurate.
Still, could have been worse, I could have paid double with the LG Sport. :laugh:
I'm not a cyclist but I've been recording my runs since the original release of the watch in November 2015. It doesn't compare to fitness focused devices like Garmin for battery life, HRM, etc., but with some trial and error I've setup mine to be perfect for my needs. I use ghostracer to record activities. It is very customisable and has many metrics to choose from. The developer is a cyclist as are many that use it, and responds quickly to questions/issues over in Google+.
I've noticed with mine the GPS is spotty if the watch contacts sweat/moisture, similar to the same issue with the SW3. I started wearing a 2" wristband under the watch for runs about a year ago and the GPS has been nearly perfect since then, in rain/snow/heat. The built in HRM isn't the best during activities but ghostracer also allows you to connect a BT chest strap for much more accuracy, since I'm wearing a wristband this is handy if I choose to use one. I also use Wear GPS (same developer) to get a lock before I switch over to ghostracer and I'm always paired through LTE to my phone that I leave in the car. I think this improves GPS as well with assisted data from the phone. I don't think they meant for the battery to last like other trackers, but I can get a few hours or more out of it and for my running that's plenty. If I ever run another marathon, I may have to find an alternative, but a half should be no problem. I've had pretty good cell signal and that probably helps but I'm sure it doesn't receive as well as a phone. For me the watch was a big improvement. Streaming bluetooth music from audio on the watch while tracking GPS and having a phone available has been great. It's nice leaving the phone behind. I just forward calls to the watch during runs.
mward1995 said:
...ghostracer ...
Click to expand...
Click to collapse
I'll look up ghostracer, thanks.
Today I was all alone with no mobile and just the UB2 running AW2 developer preview.
The battery life was about the same problem, and often, more often than with a mobile, I lost cellular connectivity. Now on reading up on AW2 that loss of connectivity may be deliberate as it turns LTE on/off as an app needs it, i.e. if the app collects data every 5 mins but waits til say 30 mins to upload, then that would mean one brief LTE enablement per 30 mins, so the fewer apps running wanting to talk to the mobile/cloud the better. I still however got about 25% battery loss per hour so in effect a 4 hour maximum usage. That is fine for runner and the shorter bike rides. I'm not clear if the cloud with an arrow through it on the display = "I can connect but I'm choosing not to" or "I can't connect".
I used Strava, and it was losing GPS and saying "paused" even when I was moving, but on getting home and looking at the ride, it seem to have fairly accurately guessed I must have been moving between getting GPS signals and estimated what I'd done in between, fairly accurately.
So you reckon a damp wrist worsens GPS? Surely your wrist is down and GPS is up so they should not interfere? It would interfere with pulse checking?
To turn 4 hours battery life into 5-6 hours of my actual ride, on long downhills I took the watch off and connected to power, I could see the green flashing of the heartrate monitor flashing, and due the weak magnetic connection to the USB cable, I was forced to ride one-handed to pinch the UB2 to its cable, but doing that I managed to top-up battery and got home without a flat battery. The Strava ride shows the periods of no pulse but otherwise looks reasonably accurate of route, moving times, mileage.
So now I know its standalone battery limits of about 4 hours, I will try it next with it BT connected to a mobile in a pocket, as then it only has to do BT not LTE, and possibly it doesn't have to do GPS as the phone does, see if that helps. I keep the mobile connected to power so its reasonably able to withstand its tasks, and hopefully the asks of the UB2 are reduced to last longer.
FYI today I had the UB2 on AW1.5 current stock and had cellular off, and it was BT tethered to my phone. I told the UB2 I was about to road cycle. It went into battery saving after about 5 hours and stopped doing anything fitness related. It did say it was using the phone for GPS and obviously it was only doing BT, not Wifi or LTE.
On Google Fit it got the time about right but the distance completely wrong. Calories quite a bit wrong too.
Basically, its rubbish as a cycling fitness device whether its standalone or tethered.
Not to come off improperly, but your review doesn't mean a whole lot since you're not using a proper app. The guy above mentioned ghost racer yet you go back out and use Google fit again and expect different results. It's like eating soup with a fork. GR is a great app. Install it, use it, then post a review.
Sent from my XT1635-02 using Tapatalk
Hi, the best accuracy i got is 5 meters (on GPS Test).
i tried Mokee and AEX and it was the same. the reception signals are good (+/- 40).
with samsung s6 i get 3 meters.
is there a way to improve the accuracy ?
thanx
Hi, I had terrible accuracy with my AEX 7.1.2 (6 meters) and since I switched to AEX 8.1.0 it improved a lot (3 meters).
I also get much better battery life.
I'm still experiencing issues with AEX 8.1 compared with stock rom where I would have GPS lock very quick and even inside buildings (near windows)
With the original rom I even had GPS reception inside a commercial plane (Airbus A320) with current rom I'm not able to lock to any satellite.
Using Waze or google maps it looses signal and driving on a highway sometimes it points me to a nearby road... Probably going back to a chinese rom to fix this