Related
Hi all,
I got an used Galaxy Nexus (unrooted, stock everything) a few months ago, with plans to use it as an outdoor gps for hiking, biking and maybe paragliding (so I wanted a barometer in it).
I live in Florida (that as you may know is all very flat... maximum altitude is about 100 meters above sea level), and I was very pleased with it (the phone, not the flatness of Florida!) until I took a trip to Colombia in December. There, I had two "bad" experiences with the Google Nexus GPS:
- I took a hike that brought me to an altitude of about 4800 m. Around an altitude of 4000 m (the last recorded point is 3992 m), the GPS lost fix and would not get it again, although GPS Status would show plenty of satellites (9 or 10) all green (that according to GPS Status help means "satellite is used while determining the location"). After rebooting and starting GPS status (but I've tried other programs too, in case you wonder) the GPS will display that it had a fix for just a second or less (coordinates would appear in the GPS Status screen, and one single point woudl be recorded, with aan altitude of 4400 m although I was probably at 4800 m) and then loose it again, never to be reacquired.
- On my flight back, I tried to record the flight. I got a fix while just before takeoff and maintained it until... 3995 m! Then, fix was lost, again never to be reacquired again (actually, I did try again when the plane was at about 1000 m, and I was able to get a fix and record the landing with no problems)
Now, for someone that likes mountaineering, 4000m is a pretty low limit! I really don't care about recording commercial flights, it's just for fun, but a GPS that stops working above 4000m while you are hiking in the mountains could mean trouble.
I've searched around the internet (including this post on XDA), but I haven't find anyone complaining about this issue at this level. Many people complain/discuss about ITAR limits, but those are much higher than what I experienced.
So, I'm wondering if is it a problem with my unit, a problem with the Galaxy Nexus, or just a coincidence? Anyone had a similar experience?
BTW, I had an T-Mobile G-2 (HTC) that worked very well both for flights and mountaineering.
Giacomo
That would explain why the gnex won't get a fix while at cruising altitude..
Beamed from my iPad Mini
Hi,
I had the same issue with my galaxy SII i9100g.
I had a mountain climbing with a summit of 4500 meters, in the beginning we really didn't need gps tracking because there was signs showing the track in the mountain. I checked the device and everything was fine the first day the signals were ok and I had my position on the phone. but in the second day when it got foggy we were in trouble as I wanted to know our altitude. and gps signals wouldn't fix. I had ten or so satellites in view but the message said "waiting for gps fix" and it didn't fix at all. I also restarted the device but it wouldn't help.
in another trip on a plane I started recording the route with gps, and I noticed last recorded point was at an altitude of 3985 meters. and when the plane reached higher altitudes i lost the fix.
I think they should give us warning about using such devices in hiking trips. it could make real trouble for me.
It might be a problem specific to the GPS receiver used in Google Nexus. Giving that I've noticed GPS late fix problems with my Nexus (compared to a Galaxy S3), I'll try checking out the internet myself too.
Have a good day!
I find it remarkable that high-tech companies such as Google or Samsung keep managing to put in design flaws or outright defects that can easily kill people. The one described here is an outstanding example. If using the GPS with good success while hiking, nobody in his right mind would ever get the idea that the GPS would suddenly stop working above a certain altitude. So some programmer has intentionally put in a deadly trap (unless you want to believe that a command like "if (altitude >= 4000) return null;" can be written inadvertently). This is sabotage of a very dangerous kind.
Another less obvious example is the design of the power button, which can easily be activated inadvertently. If somebody needs the phone to navigate and survive in the wilderness and decides to power the device down until the next critical point to keep the battery charged for a long time, the device can easily lose all power just because of an inadvertent power push in a bag or pocket. The obvious solution here is a recessed power button or, in a cinch, that the device automatically powers down again if no user action happens within reasonable time after power-up.
The rule is generally that the design is stupid, the defect is obvious, at least one solution is also obvious, and even when the flaw or defect is brought to their attention, it is not fixed. Dangerous idiots at work. Perhaps they reckon if somebody actually dies, it will be impossible to prove that the smartphone design defect was a contributing factor. It is the responsibility level of a school child.
I am sure there are more examples for this behavior.
I am not saying that people should hang their lives on their smartphones. If the smartphone is the only thing that keeps you alive, then you have already made a planning mistake. But we all know that one can get into situations inadvertently where several things go wrong in unlikely ways. In such a case you can get into a situation where your life depends on the GPS in your smartphone, and then either of the defects described above could conceivably seal your death.
My screenshot from the plain
Sent from my Nexus 5 using XDA Free mobile app
giacomociani said:
Hi all,
I got an used Galaxy Nexus (unrooted, stock everything) a few months ago, with plans to use it as an outdoor gps for hiking, biking and maybe paragliding (so I wanted a barometer in it).
I live in Florida (that as you may know is all very flat... maximum altitude is about 100 meters above sea level), and I was very pleased with it (the phone, not the flatness of Florida!) until I took a trip to Colombia in December. There, I had two "bad" experiences with the Google Nexus GPS:
- I took a hike that brought me to an altitude of about 4800 m. Around an altitude of 4000 m (the last recorded point is 3992 m), the GPS lost fix and would not get it again, although GPS Status would show plenty of satellites (9 or 10) all green (that according to GPS Status help means "satellite is used while determining the location"). After rebooting and starting GPS status (but I've tried other programs too, in case you wonder) the GPS will display that it had a fix for just a second or less (coordinates would appear in the GPS Status screen, and one single point woudl be recorded, with aan altitude of 4400 m although I was probably at 4800 m) and then loose it again, never to be reacquired.
- On my flight back, I tried to record the flight. I got a fix while just before takeoff and maintained it until... 3995 m! Then, fix was lost, again never to be reacquired again (actually, I did try again when the plane was at about 1000 m, and I was able to get a fix and record the landing with no problems)
Now, for someone that likes mountaineering, 4000m is a pretty low limit! I really don't care about recording commercial flights, it's just for fun, but a GPS that stops working above 4000m while you are hiking in the mountains could mean trouble.
I've searched around the internet (including this post on XDA), but I haven't find anyone complaining about this issue at this level. Many people complain/discuss about ITAR limits, but those are much higher than what I experienced.
So, I'm wondering if is it a problem with my unit, a problem with the Galaxy Nexus, or just a coincidence? Anyone had a similar experience?
BTW, I had an T-Mobile G-2 (HTC) that worked very well both for flights and mountaineering.
Giacomo
Click to expand...
Click to collapse
Which model is you GN?
Sent from my Galaxy Nexus
Jar3112 said:
Which model is you GN?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It's a Samsung Galaxy Nexus I9250.
I should also mentioned that in the meanwhile I have found on various forums a (very limited) number of users reporting the same problem with the same phone, but no one reporting that it works for him. So I start to be confident that it is a problem of this particular model...
Hi people,
I have recently bought a Galaxy Tab 3 7.0, brazilian version T211M with 3G and digital TV.
The idea was to use it as an in-car multimedia and GPS device using Waze. I made some tests using my Nexus 7 2013 for this purpose, and it worked flawlessly. So I bought the GTab 3 to be a dedicated tablet for this.
The thing is: the GTab 3 GPS is nowhere near the Nexus 7 GPS performance. My N7 is able to find three or more GPS satellites and lock position in a couple minutes inside my car's garage (which, BTW, is not underground, it's the building's third floor). And without A-GPS (it doesn't have 3G connection, it's the wifi version). In the same situation, the GTab 3 keeps looking, looking... and nothing. Yesterday I went out driving, and it took 15 minutes for the GTab 3 to finally lock GPS position.
Another funny thing that happens is when I stop, for example, in a traffic signal. The GTab 3 GPS gets confused somehow, it's not sure if I'm moving or if I'm stopped. Its speedometer marks 0 km/h, then 2 km/h, sometimes even 10 km/h, then 0 km/h again, the speed keeps going a little bit up, then down. Again, different from my N7, which was very precise.
As a last test, I put both tablets in my place (I live on the 9th floor), over my sofa, right beside a window and a door to the balcony. Using GPS Status (you can get it from Google Play), I tried to find GPS satellites and lock position. The N7 could do it in a couple minutes. The GTab 3 couldn't do it. I had to go outside to the balcony, stood in its end, and then finally the GTab 3 got a GPS lock. But when I go back inside, it loses the GPS signal.
I'm very disappointed about GTab 3 GPS performance, it really ruined my car tablet experience. But before I sell it and lose some money, I have to ask: is there a way to improve it's GPS performance, so that those issues are gone? Or that's the way it is, and I can't do anything about it?
I recently bought one too, haven't tested the gps yet, but comparing with my Note 3 with AGPS, it´s surely much worse.
This post talks about a gps bug?: http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=138317
Does anyone else have this issue? My GPS loses connection to the satellites every couple minutes. And yes, I have the latest map update.
Must be the bug in update. Try to use 3rd party app! Just because i never updated mine, and is working like a charm
Sent from my LG-E988 using xda app-developers app
The GPS in my phone is not very accurate. Maybe its just this phone. I only get relatively good GPS reception at night.
Sent from my LG-E980 using Tapatalk
Thanks guys. I'm starting to think it may just be this phone as well. The first map told me I was 3 miles away from my house....lol...and the second was accurate but keeps dropping the signal. I do have carhome. I'll try that and see what happens.
I also have this issue though the GPS (which is used a lot by me) was quite OK in the beginning after I bought my LG OG PRO.
I read in one of the Samsung NOTE forums that people mention the same problem claiming that the drops come when there is an "interruption" (which can be an incoming call or SMS or switching from 3G antenna to 3.5G for example). After reading this I realized that my GPS gets lost always after an incoming call plus I see at least a couple of places along my daily driving routine where GPS is lost exactly at the same place every day (making antenna switch assumption logical).
There were no any conclusions or suggested solutions in these forums, people even do not know if it is software or hardware related.
Anyone has such an issue too? Any recommendations for possible fix?
I can't believe but it seems I solved the problem with GPS - 15-20 seconds for GPS lock, no dropping and GPS test application shows very nice picture of 8-9 satellites constantly locked up while most of the signal bars are yellow (i.e. the signal strength is good).
I searched a lot as it really bothered me because I use my GPS very much plus I can say that beside this annoying thing I am very satisfied with my LG OG Pro, but nothing helped until I found this video: https://www.youtube.com/watch?v=QBpNtWvY454 (it explains the solution for Nexus 5, but my problem is identical)
Basically, the problem is that there are special contacts on the motherboard connected to the GPS antenna which is part of the back cover and the contacts are not tightened well to the GPS antenna (look at the attached picture where I put the red arrows at the relevant places). Due to the bad touch between the contacts and the antenna, the GPS does not work properly. So, all you need to do is to remove your back cover, gently "un-glue" the GPS antenna end (the rectangle part on the back cover containing 2 golden dots), lift it up a little and put a piece of paper that will tighten the antenna and mother board contacts when the back cover is returned. Good luck.
It is NFC Antenna, you cant fix GPS this way.
I have same issue, but i think NFC and GPS antennas are different. I am disassemble the phone and pull up all golden springs - but gps still very weak(((
Any solution?
same GPS problem for my g pro.
GPS is weaker and weaker
I realigned all the pins inside the phone and fixed it for a bit, but the signal was still weak. I figured it was the modem. I installed a custom rom and it worked like a charm!
I have taken my smart watch 3 running with me quite a few times over the last 3 weeks since i bought it, and i seem every time, to get some quite odd gps issues. Tried with both runkeeper and ghostracer and both are the same, which leads me to think it is the watch.
When tracking a run, the watch just all of a sudden, seems to lose GPS, no signal what so ever. Sometimes it picks it back up after a few minutes, sometimes it doesnt come back at all.
I have tried a factory reset on the watch and that didnt help at all. I have also tested this in both built up and open areas, in areas that the GPS diag tool in the dev menu says that i have access to 19 satellites, so should have no issues with GPS, but constantly do.
Is this something others have experienced? Or could this be a faulty watch?
i have had similar yet different experiences with mine.
two nights ago, had both runkeeper and ghostracer running at the same time standalone. at 3.6km ghost racer stopped tracking GPS yet runkeepr was fine.
then last night at 2.9km ghostracer again stop tracking gps. but i forgot to run runkeeper at the same time so no knowing if software or hardware.
its an annoying problem to say the least. i have mentioned this on ghostracer Google+ page.
Same problem here. Love this watch as a running watch when it works. Guess I need to start look for a normal running watch that allows me to play my music from the watch. Love the freedom of not having a phone with me.
Sent from my Nexus 6 using Tapatalk
I find the ghost racer app buggy as hell on my watch, works fine on my phone but every time i go stand alone it craps out it's got to the stage i only run it if i have my phone with me.
I have had no problems what so ever with Runkeeper so this is what i have been using on my watch can't wait till other devs get there act together and start making there apps work as stand alone on android wear.
rnscotch said:
I find the ghost racer app buggy as hell on my watch, works fine on my phone but every time i go stand alone it craps out it's got to the stage i only run it if i have my phone with me.
I have had no problems what so ever with Runkeeper so this is what i have been using on my watch can't wait till other devs get there act together and start making there apps work as stand alone on android wear.
Click to expand...
Click to collapse
GhostRacer works fine for me: better to to get 4 "steps" of gps signal before starting the run.
I have had the same awful experience since I did few test runs in the past 3 weeks with the Smartwatch 3. I tried the Endomondo and RunKeeper. both can be running stand alone on the watch. The GPS signals were easily lost and could not recover for a long period during the run. It seems to be a problem of the watch, not the apps. I had a 20k run, which ended up with only around 10k was tracked.
In the last trial taken yesterday with Endomondo, which is nice with the GPS signal strength display. I had turned on airplane mode this time. It did have some improvement. The GPS signal lost after 5k run, but I hadn't been aware of its loss until 10k. Then I click open the app and made sure the GPS signal was recovered before resuming the run. It then seems fine until end of run that totally tracked 21.2k out of the 26.3k run.
It's really a frustrating problem to have a runners' watch without proper GPS tracking.
same
i have the same problems with my watch.
after 5k the ghostracer app did not update speed and distance anymore. but the app itself was still okay because the heartrate was still changing and accurate. after 5 k more it suddenly picks up signal again. but of course all running data is useless.
after the issues with the bluetooth and google play music - now the next issue which destroys the actual reason to choose this watch.
to have a stand alone running smartwach with offine music and gps without the need to take the phone with me.
i wonder if this is a software (firmware/wear) issue and can be fixed with the next updates or in the worst case a hardware/design issue.
what do you think?
Same issue here with Endomondo. I haven't tried any other apps but for the last few days I'm getting erratic signal that will randomly stop working and usually never comes back. Really frustrating and hoping it's able to be fixed.
I tried using Ghost Racer and I am still getting constant GPS drop outs that don't come back. I've run the same course before issues cropped up with no problems at all.
Anyone have any additional thoughts on this? It's getting to be very annoying when your full run isn't tracking. Thanks in advance!
cardcowsports said:
I tried using Ghost Racer and I am still getting constant GPS drop outs that don't come back. I've run the same course before issues cropped up with no problems at all.
Anyone have any additional thoughts on this? It's getting to be very annoying when your full run isn't tracking. Thanks in advance!
Click to expand...
Click to collapse
I'm having the same issues. I contracted android wear support through chat and they are going to forward my request to their hardware specialist. They said I was the first they have heard about the issue so speak up to them, make this issue known!
I just got the 5.1 update and itching to go for a run to test the GPS. Has anyone tried since the ota and is there any difference?
Sent from my HTC One_M8 using XDA Free mobile app
AW 5.1.1 and GPS
Hi,
I have tried it (7.2km, mainly in forest) and the GPS signal has been pretty accurate.
Before the update I had a lot of issues on the same route.
So there is a chance that it is finaly fixed.
It seems that the GPS problem has been solved with the 5.1.1 update. I have had a run of 15.6K with Endomondo. It logged exactly the same. But unfortunately, the workout data was lost without being synced with phone app as usual, but the GPS problem definitely solved.
Well I guess I'm an unlucky one. My GPS has always been unreliable - not just inaccurate, but unreliable in that it will stop working part way through all of my runs. I'm lucky to get 2-3 miles before it stops working. I've tried Runkeeper and Ghostracer and it does the same on both. On Ghostracer it shows the GPS "bars", and I wait until it gets 3-4 bars before I run, then as I run it will gradually lose bars until it loses signal completely. I run on open streets with no trees or other obstructions to the sky so not sure what's going on. I upgraded to 5.1.1 in hopes that would address the issue but no such luck. Today I'm on my third ph call with Sony trying to get it RMA'd for repair.
I have yet to run without the GPS losing signal. Tried Runkeeper and Ghost Racer. Usually signal does not return. First 2-3 miles usually works pretty well. Any distance longer I lose signal. Might be heading back to Amazon before my 30 days are up.
Too early to be happy on the 5.1..1 update. The same GPS signals loss issue has come back again since the 2nd trial run. The signal lost around 3k, never coming back most of the time. Still no idea what's getting wrong.
I've been having GPS dropout problems for the last week and a half, ever since installing 5.1.1. According to someone on the Ghostracer App hangout, the problem is caused when the watch gets wet. I don't know if that's really the case, but yesterday before a run I put a layer of duct tape on the back of the watch and didn't have any problems. My previous three runs before that were all mis-recorded because of GPS dropouts.
I'm going to keep putting the tape on to see if it's really a solution.
mkddy said:
I've been having GPS dropout problems for the last week and a half, ever since installing 5.1.1. According to someone on the Ghostracer App hangout, the problem is caused when the watch gets wet. I don't know if that's really the case, but yesterday before a run I put a layer of duct tape on the back of the watch and didn't have any problems. My previous three runs before that were all mis-recorded because of GPS dropouts.
I'm going to keep putting the tape on to see if it's really a solution.
Click to expand...
Click to collapse
Tried the duct tape on the back. First longer run that I did not lose GPS. Not really loving the solution putting duct tape on every time I run.
It's absolutely the wet (sweating) causing the dropout. I had tried the duct tape approach, but still experienced the dropout after several kms, which might be due to the wet surrounding. Then I wiped the moisture off the duct tape, and the GPS signal was locked again immediately. The signals were most accurate when I simply took the watch off the wrist and held it during the run, that effectively kept it away from my sweating skin. What a design from Sony!
I'd better try the wristband approach before I decide to dump it!
So, if the moisture is really effecting it, then it would imply that the antenna is mounted in the rear, or grounded to the case. The extra moisture (conductivity from the body salts) against the case means that your body is now able to attenuate (or ground out) the antenna, thus disrupting the signal.
Noting this, i think i may take some flat clear acrylic hobby paint, and give a good layer to the back, and see if it helps. The paint should provide an insulating layer without really irritating the skin.. Can't really hurt to try..
Hey guys, replacement day is approaching, and I keep reading these articles about overheating / overdraining battery issues in the replacement Note 7.
I wanted to open a main thread about how everybody who got a replacement Note 7 is doing and if they can report any issue...
So, if you have replaced your Note 7, how is it doing?
tnx for participating!
Edited:
Check this out...
http://money.cnn.com/2016/09/27/technology/samsung-galaxy-note-7-fire-china/index.html?source=zacks
Doesn't look like a Hoax.
Whadda???
As well as the first. No issues here?
Got mine a week or so ago, no issues here. I managed to root it again using Sprint userdebug and it runs much better than the previous note did. Battery also seems to run very cool. The highest temp Ive seen was 34ºc, which is incredibly cool. That was while I was out playing Pokemon Go during a hot afternoon by the way!!
No issues here, other than occasional SD820 lag.
No problems here either...
Agreed, Jo issues other then slight SD820 lag but since the new update its far smoother than the old Note 7 I had and only has the occasional stutter.
Edit: Battery life is still fairly similarr, however, I think that's due to my personal usage.
Works great, the was a couple of minor things that were different. I can't remember what since they were so insignificant
.
Got the replacement on Sep 21
Today, Sep 25, about 11 am, my note 7 got uncomfortably warm, it can be felt both on the back through the synthetic leather cover (wallet case) and on the front, but mostly on the back.
Turned the phone off for at least 5 minutes, then turned it back on, within a minute it gets warm again, and in about 4-5 min. it gets warmer, unusually warm.
Turned it back off for at least 30 min., turned it back on again, and this time I can't even input my security PIN, the screen isn't responding.
I turned it back off, take off my 256 GB SD card.
Called Samsung (The recall Phone#), they answered right away (very surprised) told them what happened, she then told me that this is not the first time they had this issue with the new replacement Note7, she transfer me to the support department, she told me the tech support department should issue me some kind of report# or whatever, I forgot, so that I could bring that to ATT to get another replacement phone.
The support reps just told me to bring the phone to the store to get it replaced.
Went to ATT Corporate Store in Rancho Cucamonga, CA.
The sales person told me that I'm the second person with the same issue. The store can't issue a second replacement phone, she suggested me to bring it to ATT Device Support Center in Rancho Cucamonga.
But by then it's already close to 5 PM, Sunday. The office/store will be closed in few minutes.
So the ATT store clerk says to bring it to Best Buy where they have ATT reps inside to get it replaced.
So I went there, bad news....the wait is long...I decided to come back the next day.
End of story.
Now, Sep 25, Sunday night, I tried once more to powered up the Note7
It works, it didn't get warm, battery is at 40%
Put the SD card back in, and back up everything.
About an hour later, the phone gets warm again!
This time I didn't turn it off, I just stop using it and leave it on, I set the battery to "Medium Power" Saving Mode.
Battery now at 25%.
I think this time, it could be a software issue.
I remember when I change my 2009 iMac hard drive with SSD, I had to install a software to make the Fan work properly.
Samsung need to call that software company
The only issue that I'm having is when I'm scrolling through the app drawer with my finger is very slow. When I scroll with the S pen it's very fast. Other than that no complaints the phone hasn't overheated at all.
Sent from my SM-N930T using Tapatalk
I'm noticing some bluetooth issues.
It won't connect to my asus zenwatch2.
It will connect to my macbook pro for a few minutes.
I've cleared the bluetooth data and cache and turned bluetooth on and off.
Ditto on the bluetooth issues here. I use a Bluetooth continuous glucose monitor that worked great before I swapped. Cleared cache, reset, et cetera but connectivity is still intermittent.
KeeganWolf said:
Ditto on the bluetooth issues here. I use a Bluetooth continuous glucose monitor that worked great before I swapped. Cleared cache, reset, et cetera but connectivity is still intermittent.
Click to expand...
Click to collapse
I m getting the note 7 would you guys recommend me getting one
no problems at all! wonderful phone!
Exynos model here, no problems.
Replaced Exynos working well.
With new N7 I got better battery life and the phone doesn't heat up at all during fast charge (V1 did a little). If anything, the touch was not registering too well, sometimes I had to press twice to register. That was yesterday, today it's fine now, so maybe I just need to wait for things to settle, since I was downloading 3 GB of programs and data and still setting things up.
Im having bluetooth issues as well. it keeps disconnecting from my gear fit 2 and i have to manually open the app and hit connect, which works about 75% of the time. Also battery does not last as long as my previous one. its not horrible but i notice the difference.
Does anyone have gap problem in the replacement note 7?!
Devboy8040 said:
Does anyone have gap problem in the replacement note 7?!
Click to expand...
Click to collapse
yeah i can slide a sticky note along both sides of the frame and glass on mine. my previous one was almost as bad. From what I understand this is by design.
erider said:
yeah i can slide a sticky note along both sides of the frame and glass on mine. my previous one was almost as bad. From what I understand this is by design.
Click to expand...
Click to collapse
The phone have water resistant ? Or because this problem phone lose water resistant?