Related
I'm on my third G1. The first one died to some strange graphics issue where the screen would go completely pixilated and wacky on me. I think the graphics processor was overheating. On the second one the touch screen died about the same time the speaker in started buzzing during calls.
Luckly because TMobile extends your warranty 90 days every time you get a new phone, I've only had to pay for shipping. I got the latest one, and immediately installed Cyanogen 4.2.5 on it. No problems. Then I followed Michael Mayhew's instructions for the maps update to get Navigation.
I can't get the GPS to work at all. I've since tried going back to RC29, or the base Cyanogen 4.2.5 without the maps hack. I've tried other GPS applications such as the Chartcross GPSTest. I can't get a read at all on any of them. I don't know if it was working before the updates, because I never tried to use maps before I installed the mod.
So I'm wondering somehow a radio update was applied that broke this phone, or if there is anything I can do to change the gps drivers around. Anyone with similar GPS failure issues?
I don't really want to return this one as I've only had it one day!
Yes, similar issues. No solution thus far. I also did not test GPS before flashing. OOPS?!? And now it no longer works, but I can't tell if that was the case to begin with.
I followed the same procedure (CM 4.2.5, Navigation mod), and had the same result--broken GPS. "My Location" not working, "Searching for GPS" forever, etc.
So two possibilities I can see:
1) hardware problem w/GPS
2) one or a combination of CM 4.2.5 + Nav = broken GPS
I have seen a few people on these boards say their GPS doesn't work all of a sudden. In fact, there are stock Droid owners with issues.
Can anybody chime in?
Hmmm
So for about 10 minutes on Friday it started working again. Totally random, I have no idea why. I was at a party and decided to see if it was working. All of a sudden I had signal (using GPSTest) and google maps found my location.
I've since tried it several times, rebooting, and doing a bunch of other stuff. I can't get it working again. Total fluke! So frustrating!
Well now the new version of google maps is in the market. I've successfully installed that one but still no GPS.
Im having the same issue on my G1 right now. Sorry for the Zombie thread, but did this ever get resolved?
I've had the gps fail on my phone and others I know have also. The g1 seems to have issues with the gps antenna strip breaking internally so one minute you'll have reception, the next.. nothing. Only solution is to find a new antenna strip and replace it (good luck!)
Aside from possible hardware failures, the GPS units on these phones tend to be very weak. Sometimes it *IS* impossible to get a strong enough signal to lock on, even when out in the open if there is something nearby that can reflect the GPS signals.
However note that these are AGPS devices, which means that with a cell connection and a data connection, and given that google knows the coordinates of the cell tower you are connected to, it is able to load assistance data (almanac + accurate time synchronization via NTP), and this will *GREATLY* improve your chances of getting a good lock and greatly reduce the time it takes.
Woil said:
I'm on my third G1. The first one died to some strange graphics issue where the screen would go completely pixilated and wacky on me. I think the graphics processor was overheating. On the second one the touch screen died about the same time the speaker in started buzzing during calls.
Click to expand...
Click to collapse
I doubt that it was the GPU overheating. Your phone would burn your hand if it got that hot.
The in-call buzzing could be corrected by shifting the screen a little bit while it is happening. It is related to GSM interference with the speaker. The speaker is literally playing the radio waves emitted by the phone. The touchscreen issue was probably a broken cable... also related to moving the screen.
Luckly because TMobile extends your warranty 90 days every time you get a new phone, I've only had to pay for shipping. I got the latest one, and immediately installed Cyanogen 4.2.5 on it. No problems. Then I followed Michael Mayhew's instructions for the maps update to get Navigation.
I can't get the GPS to work at all. I've since tried going back to RC29, or the base Cyanogen 4.2.5 without the maps hack. I've tried other GPS applications such as the Chartcross GPSTest. I can't get a read at all on any of them. I don't know if it was working before the updates, because I never tried to use maps before I installed the mod.
Click to expand...
Click to collapse
Note that you are getting refurbs....
So I'm wondering somehow a radio update was applied that broke this phone, or if there is anything I can do to change the gps drivers around. Anyone with similar GPS failure issues?
Click to expand...
Click to collapse
What radio version are you running?
I've also had no luck getting a GPS signal ever since I installed hacked navigation... I wonder if that's the problem? Has anyone tried removing the hacked navigation, to see if that solves the problem?
BTW, the problem started on CM 4.1 with EBI0 radio (2.22.19.26I), and still persists with CM 5.0.7... Has anyone tried upgrading their radio to 2.22.23.02? How about the folks that have gone back to the Updated Rogers EBI1 Radio (3.22.26.17)?
I have been having the "searching for gps" problem as long as I can remember (although I just got this phone a month or two ago)....I remember trying to install the hacked navigation or something so maybe that messed it up?...this phone was never opened, and I would hate to have to open it up to see if it is a hardware issue because I may not put it back as it was. IDK what to do, I even started a thread about it and tried every solution I could find and nothing worked for me....
I wish someone could chime in here with some insight...but it is also nice to hear others with this issue and their advice/ideas also...
Has anyone tried un-rooting and returning the phone back to complete stock and wiping everything ? has that worked for anyone?
Original, I thought I was left out of the GPS problem with the Samsung Vibrant, thinking it was about when you used GPS ...but with the Navigation
However, today, I was using the Google Search function, or something that simply invoked the GPS, but not fully using the Navigation, then it cut out, and I couldn't see anything for about 30 seconds, then it restarted fine.
THAT, please assure me is the problem that people were originally speaking of
I dont mind being wrong about what I thought it was ORIGINALLY. i.e. navigation being used
But please tell me that what I described is the problem and NOT a more serious problem that is gonna involve me having to get a new phone.
I had the NEXUS and one of the 3 I had turned off two or three times a day. They said it was NOT normal, and then I had to replace it..
I am hoping and leaning to believing that this problem is what you all have described as the original GPS problem cutting off
thanks
The original and core problem with the GPS which still exists is that the GPS cannot lock on to more than one or two satellites even though there are many more in view. The result is inaccurate and inconsistent position information being fed into whatever program uses GPS. People will notice symptoms more with nav apps but it will also affect browser location and google search (with location) as well. So your symptoms may be a result of of the common bad GPS problem. Personally I believe that ALL Vibrants have a faulty GPS as I have tried at least a dozen showing the exact same faulty behavior. The best way to determine if your phone has a buggered GPS is to test it using something like GPS Test and see how many satellites lock VS how many are in view (discovered). A fully functioning GPS will lock on no fewer than six sats with nine to fifteen visible.
Thank You XfooYen...and thanks for being Quick
I do not know how to do the test. Might you be able to and have to time to explain how simply and what I need (via apps etc..)
But bottom line, to hear that it is basically, maybe not fully, partly to do with the GPS makes me feel better.
At least it is not cutting off WHEN i am NOT using the GPS, 3-4 times a day, like my first android phone, Nexus
thx
Does the European Galaxy S have this issue? If so, then I fear that a solution is unlikely to be at hand, given that this version has been out for a while, and would point to a design flaw in the hardware that cannot be fixed with software.
That's the big unknown-is it hardware that's defective, bad firmware in the controller for the GPS chip, or a system software problem?
yeah, no one knows if it's firmware or hardware or both. Only time will tell. We all hope it's just firmware.
To OP, you can find GPS Test in the market. There are many ways to see what your GPS is doing exactly. Rather than me explaining it, I recommend you search youtube for examples of GPS testing in action.
A thing to consider is weather you can return the phone with a full refund. If so, I recommend it. You can then wait until a real fix is pushed out and repurchase when it does.
Sent from my Vibrant using XDA app facing north...no, wait. southwest.
Thank you for pointing out where to find the gps test Next i will look into doing it I also appreciate feedback on what the proper could be To summarize it seems like no 1 knows what the problem could be i may know more once the gps test is done next i think most would agree i m not looking for a wii fun on this fabulous phone n next correct me if i am wrong i hope work for t mobile 4 a while and have been there 11 years most phone companies you can't get a full refund out of the buyer's remorse period
i actually believe most of you will think i am right or at least the grateful to want to wait until the problem is saw. It is not the worse in the world once i find out that use it i will wait on the 6 once they say this symptom is clearly not related names if it persists i may ask for a replacement. Until then any support or advice in simple terms, LOL, Would be appreciated. I just saw a thread with the term gps fix with another link does anyone know if that works .
Thanks again so much Please remember this was typed or not typed using the speech to text feature. I have issues that make my hands shake head hurts and issues much better for typing
In sending my last post i head something popped up that said Something beta OR traditional Wouldn't that have something to do with this thread for the entire site on my vibrate
Please, somebody tell me there's hope. 2 really annoying & disappointing things are happening. My bluetooth keeps randomly disconnecting, and to make matters worse the status bar icon still shows it is connected, but it's not. Second, I am dropping calls almost daily, and I'm mostly in places where 2 seconds before the drop I had 4 bars!!! I went to a store today & got a replacement SIM (50.01 vs. 39.01 markings) hoping that might solve it, not happening. And the signal strength almost never shows less than -105 dBm, sometimes -97. I NEVER had a dropped call or any bluetotth issues with either my old trusty G1 or the MT3G I just came from. I'm really trying to love the phone, it has so many positives. But the fact that it's a "phone" and it's basic function is skewered is pissing me off big time. Please, someone tell me I ain't the only one experiencing these issues, and, that either the OTA FroYo or Cyan's first ROM is gonna fix 'em? Better yet, any known fixes now? Are these issues in any way related to the data issues, possibly? When I called Tech Support last night they said to try a hard reset, but I really don't want to do so, unless I can flash one of the stock/de-TW'ed "stock" ROM's written about in the Dev. threads. Anyone have any concrete suggestions or explanations? Thanks...
I'll try to make this quick. When making phone calls with my Nexus 4, I'm experiencing two issues.
1) I sound choppy to the other person. For example, I'll be talking and I'll be going in and out. I've tested this with different callers and it's true for all of them. They all say I sound choppy.
or
2) Sometimes, neither of us will hear each other for a few seconds before sound returns. Like, I'll say something, and the other person will sound quiet, and I'll go "hello?" and they'll say "I said, oh okay." As if it didn't get the immediate response. The same thing happens vice versa, where I'll respond and they'll ask if I said anything cause they didn't get it.
Issue 2 happens a lot less. It's issue 1 that is driving me nuts.
Is anyone else experiencing this?
I'm on Tmobile and I've switched SIM cards twice, tested the network with my family's phone that are part of the same plan (perfect call quality, so I don't believe it's Tmobile), and I've had Google replace my phone. The RMA still has the same problem, so I'm reaching out to the forum to see if anyone else is experiencing this too, and more importantly, has a solution or at least know what's the culprit.
This only started happening with the Nexus 4. When I had my Galaxy Nexus on the same line and network, calls were fine.
I called Google a second time, and they could immediately hear what I was talking about. The choppiness was really bad, they said, and they insisted that it's hardware related (though I'm not convinced. Could I have gotten two defective Nexus 4's in a row? Possible, I suppose). They convinced me to give it one more go, and so I'm waiting for another RMA to arrive.
Any thoughts, help? I haven't been able to find much on the web about it.
Thanks.
If you got 2 defective Nexus 4s in a row it's either you are really unlucky or it's a signal related issue, like your signal could be weak causing choppiness, or maybe a problem with your carrier? I guess. You should probably try a 3rd time before looking for your carrier and asking them about the signal. Try moving your SIM card to another phone to see if it's the problem with the carrier. If it's ok on another phone, get it replaced a 3rd time I guess.
Good luck
This poll is simply to help determine whether there are hardware variances out there which will resolve the GPS lock dropping out, after some period of usage, issue.
There are many "workarounds" to help alleviate the issue, including limiting your usage to just Google Maps, updating Google Play Services, wifi options, clearing AGPS, etc.
What I'm interested in is whether anybody was able to maintain their normal usage and just swap out a unit and have the GPS issues resolved.
I'd like to isolate out folks whose GPS works fine simply because their normal usage pattern doesn't trigger the issue. By focusing only on folks that are triggering the issue who have exchanged their units, we can see if there are potentially hardware variances.
If there are a very low percentage of cases where a replacement fixes GPS, then it doesn't make sense for folks to keep exchanging their unit(s) hoping the new one fixes the problem. In this case, if GPS is really important, either take a chance waiting for Google to fix it (if they can) or return the unit and wait until it is resolved.
This poll will not tell you whether this is ultimately a hardware, software, or some combination issue. That requires understanding the root cause, which cannot be determined in a poll.
If your exchanged unit resolved GPS for you, please post
first 9 digits of "KBC" SSN number
build date from the box label
16 or 32gb
Code:
[B][U]For example[/U][/B]
SSN: D60KBC265xxx
Date: 2013.06
16gb
This will help figure out if there are any build/manufacturing patterns.
I voted no to see The poll.... I dont have my nexus yet. I hope I don't have any GPS issue that's the Main reason I traded my iPad mini for, that and the fact that I can pocket my tablet now
adeon said:
I voted no to see The poll.... I dont have my nexus yet. I hope I don't have any GPS issue that's the Main reason I traded my iPad mini for, that and the fact that I can pocket my tablet now
Click to expand...
Click to collapse
There is a 'View poll results" button. No need to 'fake' results by voting when you are not giving any proper answer.
adeon said:
I voted no to see The poll.... I dont have my nexus yet. I hope I don't have any GPS issue that's the Main reason I traded my iPad mini for, that and the fact that I can pocket my tablet now
Click to expand...
Click to collapse
For many people if ALL you use is google maps, no navigation, no earth, no gps status, no waze, etc. then you can get many of the units to hold lock for a while, possibly indefinitely.
However, a lot of people use a couple of gps apps and that is where the issues come up.
I guess fewer people use GPS on the tablet versions than the phone/tablet-with-mobiledata versions because their gps apps require data connections, which they may not have access to on the go, but many people still do have apps that work without a data connection or they tether the device.
So only 9 folks have actually exchanged the unit for GPS problems and found this thread? I would have expected more people would have exchanged given how many people are experiencing the problem on the GPS lockup threads.
People aren't exchanging because Google has said they are working on a fix. This implies it's a software issue that will be patched.
Obveron said:
People aren't exchanging because Google has said they are working on a fix. This implies it's a software issue that will be patched.
Click to expand...
Click to collapse
I have never read they are working on a fix, just that they are looking into it. Please post where it says what you are suggesting.
To me "looking into it" and "working on a fix" are quite different levels of commitment from Google. Keep in mind if the problem is on the proprietary hardware side (likely Qualcomm) and/or with Asus who hooked everything up, Google would need to interface with them for a solution (if any) so it would be very hard for them to unilaterally say they are "working on a fix" without even knowing what the root cause is.
Here is the latest info from Google's "official" community manager Paul Wilcox
http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/prfUDZA7M2s
Jul 30 - Paul Wilcox
Thanks for the reports everyone, we're looking into it.Aug 2 - Paul Wilcox
Hi again everyone,
Could you please let me know a couple of things about your experience with GPS on your Nexus 7 tablets?
1. Do you still encounter this issue if you visit Settings > Location access > Access to my location = on as well as WiFi & mobile network location = checked?
2. If you visit Google Maps or another program that displays your location, is the app actually getting your location even if the GPS notification doesn't seem to show a tight GPS lock? Or is it unable to pinpoint your location?
Thanks!Aug 5 - Paul Wilcox
OK everyone, thanks for confirming my questions from a couple of pages ago, as well as the info that disabling Google Play Services seems to be a workaround. My Android engineering colleagues are investigating this issue.
By the way, in case you're not aware several components of Android use Google Play Services so disabling that can have some unintended consequences on the functionality/performance of your device. For example the Hangouts app won't work without enabling Google Play services.Aug 6 - Paul Wilcox
On Tuesday, August 6, 2013 8:18:48 AM UTC-7, Kenny Bateman wrote:
Also I'm wondering if anyone from Google ever responds on here. Some/any input would be great!
Yup Kenny, Googlers are present in this forum. See my response about this issue a couple of pages back on this thread.
No update for the community about this at this time, but the team is aware and investigating.
Aug 9 - ArsTechnica
Google's Paul Wilcox has been active in that thread telling users that Google was "looking into" the problem and asking some follow-up questions—it's unclear as of this writing whether the issue will be fixable in software with an update or if it's indicative of a deeper hardware problem. We've reached out to Google for further comment on the issue and will update this post if we get a response.
Update: Google's official response is that they're aware of the issue but not ready to comment further at this point. We'll continue to follow the story as it develops.
Since then complete radio silence.
When Asus last had GPS problems with the Transformer Prime, their "solution/fix" was to give people $17 and a free GPS dongle (they even claimed the Transformer Prime didn't include a "professional" GPS). This came after a class-action lawsuit and only residents of the US could officially file a claim:
Settlement: Asus to give GPS dongle and $17 to Transformer Prime users
http://www.androidauthority.com/asus-transformer-prime-settlement-183316/
http://event.asus.com/ASUSPad/TF201GPS/
I haven't returned mine...I mean what is the use? Also my screen is working excellently with no multitouch issues, I do not see any dead pixels and the screen bleed is fine. So what am I supposed to do? I don;t want to tempt getting a worse machine but the GPS not working sucks...kinda stuck...
AnarchoXen said:
I haven't returned mine...I mean what is the use? Also my screen is working excellently with no multitouch issues, I do not see any dead pixels and the screen bleed is fine. So what am I supposed to do? I don;t want to tempt getting a worse machine but the GPS not working sucks...kinda stuck...
Click to expand...
Click to collapse
Not suggesting you personally should exchange it, though based on your confidence level you'll get a resolution you are satisfied with (or you really don't need GPS), you may need to consider whether to return it or just take a risk.
Just trying to get feedback from those that already have, which of course there will be some.
So far from the polling it is looking like it is pointless to return it though. That could change if some people find units that work for them.
It does make you wonder if every unit has the same GPS problem and the people who report GPS works fine just have a usage pattern that doesn't trigger it (which may be perfectly fine for them)
How do you tell the build date?
dannycalgary said:
How do you tell the build date?
Click to expand...
Click to collapse
It is on the label on the top and bottom of edge of the white box.
It'll be something like 2013.06, 2013.07 (or in the future 2013.08)
sfhub said:
To me "looking into it" and "working on a fix" are quite different levels of commitment from Google.
Click to expand...
Click to collapse
Fair enough sfhub, I guess I interpreted Google's commitment differently. It seemed to me that "looking into it" implied they are troubleshooting, which appeared to me they were commited to fixing the issue.
They asked about google play services, and were interested to hear that it affects the stability of the GPS. That alone, seemed to imply (in my naive perception), that software has an intergral role in fault.
I interpreted the semantics differently than you, and basically deemed that I personally wouldn't return the Nexus as there is a good chance Google could patch the problem.
However, after reading your excellent breakdown of Google's communication, I see your point of view. I am therefore much more concerned that it is a hardware fault. I still remain blindly optimistic that it is a software problem. After all, the GPS can be stable under certain software circumstances (disabling google play, using only specific apps, and only one at a time).
Don't get me wrong, I would love the problem to be fixable in software and have a gut feeling that it can (because I can use just Google Maps and nothing else and it won't drop) but without any knowledge of the root cause that is purely a guess/gamble.
Paul Wilcox mentioning Google Play Services was actually in response to a couple of users posting they had disabled Google Play Services and it helped their GPS situation. It wasn't something Google determined on their own and was reaching out to the community.
I'm skeptical that is the issue as I have Google Play Services disabled and I still get the dropouts and other folks have mentioned upgrading Google Play Services helped their situation while others mentioned downgrading helped their situation.
If I were to guess, Google Play Services may have some effect on the issue, but isn't the root cause.
IMO "looking into it" just means you've gotten past the PEBKAC-meter.
D70KBC-155xxx
2013.07
32GB
I purchased this unit from the Google Store and received it this morning. I own a nexus 7 2012 and it has always worked fine. So I knew how to set up the GPS. After trying for an hour I phoned Google Support and and was sent on reams of useless apps that really did not have anything to do with the GPS. When she asked me if I could see my location on the google map I told her yes but only because I was hooked up on WIFI. The we went on a 15 minute discussion on the fact the tablet was not outside. I told her the other tablet which was more than 5 feet further to the window was working just fine with 11/12 SAT/FIX. This was a very painful part of the conversation. Finally she offered to have me download apps that would not need the GPS and make do without it.
At this point I told her I was getting somewhat upset and asked her to pass me to someone else. I basically went through the routine all over again and I finally told him I would send the unit back and have my credit card reverse the charge. That seem to wake him up. He then offered to send me a new unit and for me to hold to this one until the new one comes in. So that is where we are right now.
This was the first time dealing with google support and I sure was not impressed.
no problem so far
ive been using the gps for a good amount of time and i haven't had an issue yet
aptech said:
ive been using the gps for a good amount of time and i haven't had an issue yet
Click to expand...
Click to collapse
Don't take this the wrong way but the thread is looking for people who have a GPS problem and got a replacement unit to try and resolve.
It seems you never had a gps issue.
sfhub said:
Don't get me wrong, I would love the problem to be fixable in software and have a gut feeling that it can (because I can use just Google Maps and nothing else and it won't drop) but without any knowledge of the root cause that is purely a guess/gamble.
Paul Wilcox mentioning Google Play Services was actually in response to a couple of users posting they had disabled Google Play Services and it helped their GPS situation. It wasn't something Google determined on their own and was reaching out to the community.
I'm skeptical that is the issue as I have Google Play Services disabled and I still get the dropouts and other folks have mentioned upgrading Google Play Services helped their situation while others mentioned downgrading helped their situation.
If I were to guess, Google Play Services may have some effect on the issue, but isn't the root cause.
IMO "looking into it" just means you've gotten past the PEBKAC-meter.
Click to expand...
Click to collapse
Did you reboot after disabling Google play services? That was the only way I could get it to work.
Disable and delete updates
Reboot
GPS works in navigation now
You get a ton of notifications to enable it again, but most apps still work fine without it.
Sent from my Nexus 7 using Tapatalk 4
sleepnmojo said:
Did you reboot after disabling Google play services? That was the only way I could get it to work.
Disable and delete updates
Reboot
GPS works in navigation now
You get a ton of notifications to enable it again, but most apps still work fine without it.
Click to expand...
Click to collapse
Yes, I have no updates at the moment, just what came stock, froze play services, rebooted.
I can get GPS to work indefinitely if I only use Google maps.
Once I use other GPS apps, including Google nav, it will lose ability to lock anywhere from 5 to 40 minutes
Sounds like a driver issue. Anyone try CM and if you get better results?
CM use their own kernel and drivers so you should get different results. That should prove it would be fixable in software.
Sent from my Nexus 7 using XDA Premium 4 mobile app
The issue is very intermittent. Today I wasn't able to reproduce with 2hours of GPS on. I have tried both stock and CM and had the bug on both.
Yesterday I lost lock consistently after 15-25mins on but rebooting would return it to life which makes me strongly believe it's fixable with software so I'm not too worried.