There are a few threads on the various Froyo releases, their features bugs etc. but nothing that touches on Froyo's GPS issues specifically.
I'd like to know whether anyone has successfully changed the 'look ahead' behavior that all the Froyo firmwares come with so far.
For those who have not experienced, i.e. not YET noticed this 'feature', here is a brief description:
On Froyo the GPS is showing you exactly where you are even while driving at speed. There is no delay whatsoever. All is well while you are going in a straight line.
The problems begin when you either stop abruptly or take a sharp turn. It then takes the GPS up to a few seconds to come to terms with what just happened. I can only assume this is due to some software component 'smoothing' the path by making up positions, i.e. looking ahead.
I uninstalled JPH and JPK. GPS doesn't do me any good when I see myself still driving down the same road after I took a right turn 5 seconds ago. JM8 and a number of other Eclair firmwares do not suffer from this.
Has anyone successfully 'downgraded' the GPS component of Froyo? Is this even possible? Is there a way to disable the 'look ahead'.....somewhere hidden in settings or some hidden menu?
ewok666 said:
Has anyone successfully 'downgraded' the GPS component of Froyo? Is this even possible? Is there a way to disable the 'look ahead'.....somewhere hidden in settings or some hidden menu?
Click to expand...
Click to collapse
Did you turn on the "Use Sensor Aiding" feature? That's new in Froyo. Try turning that off. It's in the Location menu.
hardcore said:
Did you turn on the "Use Sensor Aiding" feature? That's new in Froyo. Try turning that off. It's in the Location menu.
Click to expand...
Click to collapse
Thanks. I thought I had that disabled. Is this on by default? I'll give that a try next time I load a Froyo firmware....if there was a quick way to nandroid back without an Odin restore, EFS fixup plus all the Voodoo conversions that would be sooner rather than later ;-)
ewok666 said:
Thanks. I thought I had that disabled. Is this on by default? I'll give that a try next time I load a Froyo firmware....if there was a quick way to nandroid back without an Odin restore, EFS fixup plus all the Voodoo conversions that would be sooner rather than later ;-)
Click to expand...
Click to collapse
The default is off
It greatly helps when it's on I think
Arkanius said:
The default is off
It greatly helps when it's on I think
Click to expand...
Click to collapse
Isn't it meant to aid while walking? I can see that this may be causing when driving.
Well, there is absolutely no reason this option to decrease performance.. At least shouldnt be, unless Samsung screwed something up as usual. (which actually may be the case)
I had mine set to "off" by default. There is next to no difference while driving.
xan said:
Well, there is absolutely no reason this option to decrease performance.. At least shouldnt be, unless Samsung screwed something up as usual. (which actually may be the case)
I had mine set to "off" by default. There is next to no difference while driving.
Click to expand...
Click to collapse
As I said in the OP, I've always had the issue that GPS took seconds to realize that I changed direction or suddenly stopped. I'm just guessing that something that is intended to help stabilize GPS at slow speeds (walking, swimming with the dog, etc.) might cause a similar effect while travelling in a car.
swimming with the dog? I shat bricks ;d
Anyway, yes that right. Since its like phone is calculating from the sensor (compass, g-sensor -> speculating here) reads the approximate direction and pace you are moving at. It *might* be a problem with g-sensor read, becouse I find it quite flaky (using gps testing utilities exposes its terrible lag and low sensitivity)
BTW is it better after disabling it?
xan said:
swimming with the dog? I shat bricks ;d
Anyway, yes that right. Since its like phone is calculating from the sensor (compass, g-sensor -> speculating here) reads the approximate direction and pace you are moving at. It *might* be a problem with g-sensor read, becouse I find it quite flaky (using gps testing utilities exposes its terrible lag and low sensitivity)
BTW is it better after disabling it?
Click to expand...
Click to collapse
Well, there was a guy in another thread who claimed his Galaxy GPS was spot on. To proof that he uploaded a track of his walk with the dog and it clearly went right through the river a couple of times........I thought THAT was hilarious! ;-)
I might flash Froyo once again and play with that setting......still hoping that the Galaxy CAN do acceptable GPS. :-|
i'm mostly happy with the gps software on JPK (compared to JM8 which was already better than "official")
but the lag you're speaking about is killing me. there's waaay too much delay. sure it makes nice recorded tracks, but using it you'll see its crap
going to try my track with aiding stuff off tomorrow although im not sure its going to help
Well i am using JPK and the MOTONAV is running......ok, but i got "GPS LOST SIGNAL" every 10 minutes and the map jump around, after 10 seconds it will find signal again and back on track. anoying.
I borrowed an iphone 4 to test that thing's GPS and compare it to the Galaxy.
I have attached the Horror kml track file. It's no better, if not worse, than the Froyo stuff. I certainly did NOT expect that!
The kml can be viewed with Google earth and other GPS programs.....
And for the record....I did drive ON the road at all times ;-)
There is a new trend obviously. The more expensive the phone, the more messed up the GPS. LOL
What a total fail for the high-end devices these days.
bilboa1 said:
i'm mostly happy with the gps software on JPK (compared to JM8 which was already better than "official")
but the lag you're speaking about is killing me. there's waaay too much delay. sure it makes nice recorded tracks, but using it you'll see its crap
going to try my track with aiding stuff off tomorrow although im not sure its going to help
Click to expand...
Click to collapse
did not help ;D
bilboa1 said:
did not help ;D
Click to expand...
Click to collapse
Bummer......
Maybe they looked at the iPhone and thought it was a great 'feature'.
Oh man, if 2.2 firmware didn't get the GPS issues resolved, then it's pretty much useless for me. I'm happy with the overall phone as it is, minus the GPS issues.
stan28 said:
Oh man, if 2.2 firmware didn't get the GPS issues resolved, then it's pretty much useless for me. I'm happy with the overall phone as it is, minus the GPS issues.
Click to expand...
Click to collapse
The GPS issues will NEVER be resolved - it's a hardware problem. You probably just won't ever get Samsung to admit it, now they try those lame "sensor aiding" dirty fixes, but that's just another proof that it's a hardware problem - why else would they spend time doing the sensor aiding?
EDIT: I hope Samsung proves me wrong
MoWa22 said:
The GPS issues will NEVER be resolved - it's a hardware problem. You probably just won't ever get Samsung to admit it, now they try those lame "sensor aiding" dirty fixes, but that's just another proof that it's a hardware problem - why else would they spend time doing the sensor aiding?
Click to expand...
Click to collapse
PROVE IT!!! You are presenting hypothesis as fact, and that might be acceptable in places such as Digg, but it is inappropriate on developer websites.
Also, how do you know that sensor aiding required much much work? After all, it's predictable polling from already working/predictable sensors, unlike GPS sensors which pick up a fuzzy idea of where you are, is affected by satellite coverage, etc.
Sensor aiding can assist even GOOD GPS receivers indoors, tunnels and in areas where signal can drop (heavy trees, huge skyscrapers). Yes, even on Garmin units, this can be handy. We all know that the faster you travel the greater inaccuracies which are incurred, and this can help reduce inaccuracies in those scenarios. There are plenty of reasons to implement this functionality, and not all point towards bad hardware. Samsung probably has a few groups of programmers being thrown at different problems, because programmers aren't scalable, and there is a limit to the number of developers which can work on a specific issue/bug/improvement.
andrewluecke said:
PROVE IT!!! You are presenting hypothesis as fact, and that might be acceptable in places such as Digg, but it is inappropriate on developer websites.
Click to expand...
Click to collapse
I can't prove it - but I can use my brains to put together the circumstantial evidence. Sorry if that isn't good enough for you.
MoWa22 said:
I can't prove it - but I can use my brains to put together the circumstantial evidence. Sorry if that isn't good enough for you.
Click to expand...
Click to collapse
You SAID "The GPS issues will NEVER be resolved - it's a hardware problem", and spreading random rumors like that makes XDA appear unprofessional, and benefits nobody. I've just simply noticed a recent trend towards guesses being slowly changed to fact here in XDA developers, and I'd like to try to reduce the frequency of that happening
Related
So, all those who have upgraded the firmware to Froyo, please answer this.....
Is your GPS/Google Map finally working in perfect condition?
If the GPS still have problem then i think we can probably say with high degree of certainty that it is a hardware based problem....
I mean with all the firmwares that they have leaked so far, wouldnt fixing the GPS issue be priority number one for them? If it was software/firware fixable, then i would think that they would have solve it by now....
widjaja74_us said:
So, all those who have upgraded the firmware to Froyo, please answer this.....
Is your GPS/Google Map finally working in perfect condition?
If the GPS still have problem then i think we can probably say with high degree of certainty that it is a hardware based problem....
I mean with all the firmwares that they have leaked so far, wouldnt fixing the GPS issue be priority number one for them? If it was software/firware fixable, then i would think that they would have solve it by now....
Click to expand...
Click to collapse
If they haven't fixed it yet for us on Eclair what would make you think FroYo fixes the problem?
heygrl said:
If they haven't fixed it yet for us on Eclair what would make you think FroYo fixes the problem?
Click to expand...
Click to collapse
The next official release will be Froyo, so it makes sense they do not work at eclair firmware anymore. So if they fix GPS it will be with the next official firmware and this should be Froyo.
Bajo76 said:
The next official release will be Froyo, so it makes sense they do not work at eclair firmware anymore. So if they fix GPS it will be with the next official firmware and this should be Froyo.
Click to expand...
Click to collapse
They need to patch the GPS before September. If they had a patch we would be hearing about an OTA and it would be included in later leaked firmware revisions.
the gps is fixed (at least for me) in JM2 already!
jodue said:
the gps is fixed (at least for me) in JM2 already!
Click to expand...
Click to collapse
Not for me. JM2.
Its much worse on froyo.
But its perfect on JM2 if you use -
http://forum.xda-developers.com/showthread.php?t=732030
and
http://www.intomobile.com/2010/07/21/t-mobile-samsung-vibrant-galaxy-s-gps-issues-fix-tutorial/
Are you going back to the SGS if/when they fix it? Thought you sold yours.... But im old and might have you confused with someone else
Sent from my GT-I9000 using XDA App
The GPS is still useless in Froyo. At least for me...
ml78 said:
Are you going back to the SGS if/when they fix it? Thought you sold yours.... But im old and might have you confused with someone else
Click to expand...
Click to collapse
Yeah my exact thoughts. Dude didn't you say 2 weeks ago that you sold your SGS? Did you even have one?
Yes sirs..... i sold mine couple of weeks ago ...
i couldnt find any good or better android phone ever since... all have their flaws in one way or another... so if they fixed the GPS issue, i might go back to this phone because it still offers the best features compared to others....
i'll probably wait to see until september wether they have fixed this GPS issue or not.....
Iphone 4 seems to have the phone signal problems taken care off in their later batches of production phones... so i might consider that phone too if that is really the case.....But still, i hate the thought of having to cut up my sim cards just to be able to fit in the phone... it will give me problems when i want to use the sim on other phones.... i think the use of different size sim card is totally dumb move on steve jobs.....its a differentiation feature that offers no benefits at all but headache....But coming from someone who said "you are holding it the wrong way" about a phone, it is no surprise for me......
So smart yet so stupid....
Wierd post..
Sent from my GT-I9000 using XDA App
GPS on my Galaxy S works perfectly on all firmware, so if gps does not work on yours it must be a hardware problem. Take it back.
Sent from my GT-I9000 using XDA App
Why with froyo, if is a software issue must be broadcom driver problem libgps.so ,
android interface with driver gps.h is clear(http://pdk.android.com/online-pdk/guide/gps.html).
So you "only" have to replace the driver and possibily related config files.
If GPS is capable of 24 satellites (bcm4751 seems a good GPS chip) simultaneus tracking why only can lock 8 (this is not explainable).
Excuse my poor English.
justmevagyok said:
GPS on my Galaxy S works perfectly on all firmware, so if gps does not work on yours it must be a hardware problem. Take it back.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
And ignorant comment of the day goes to.....drum roll please....
Sent from my GT-I9000 using XDA App
jodue said:
the gps is fixed (at least for me) in JM2 already!
Click to expand...
Click to collapse
please stop saying bull****....
the fix time is not the GPS problem
try copilot or navigon and use the GPS in your car, then you will how bad the GPS is
justmevagyok said:
GPS on my Galaxy S works perfectly on all firmware, so if gps does not work on yours it must be a hardware problem. Take it back.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yeah sure .... using the GPS with GPS test in your house and having a fix in 10 sec is the main use of a GPS ... at least for all people saying it work
Just for information, the main use of a GPS is for car navigation, and there the GPS is kind of useless .....
widjaja74_us said:
if they fixed the GPS issue, i might go back to this phone because it still offers the best features compared to others....
Iphone 4 seems to have the phone signal problems taken care off in their later batches of production phones...
Click to expand...
Click to collapse
It's more likely that the flaw is in software than hardware, and samsung has said multiple times that they are looking into it, so i bet there will be a fix for it.
The problem with the iPhone is that you can't fix a design flaw, without new design, understand? See, when you connect 2 different antennas with your finger, you kill them both.
Anyhow, if you even consider iOS over Android, then i guess Android itself just isn't for you. The thing in Android is customization and if you don't like that, then you're better off with Apple products. I tend to recommend iPhone for girls and hipster friends, because they don't understand anything about personality or care about the latest and greatest hardware.
[offtopic rant]
In fact, Apple products scare me a little bit; so much fanaticism. I happen to work in a web development agency and we have to use mac's. Everyone except me in my office praises Apple and i absolutely hate it, mainly because my WIN 7 machine at home is just, well, multiple times faster and better for everything (crapbook in work is the latest and greatest). To me it seems that they are in some sort of vista (before SP1) hating time continuum; they can't escape, even though snowleopard is a joke update to the previous cute cat. They seem to hate all Microsoft, because of IE6 and vista(before sp1); even though they have **** like iTunes, QuickTime and well OSX(my honest opinion, have to use snowleopard every day).
[end rant]
Good luck!
pepitodequetequejas said:
Why with froyo, if is a software issue must be broadcom driver problem libgps.so ,
android interface with driver gps.h is clear(http://pdk.android.com/online-pdk/guide/gps.html).
So you "only" have to replace the driver and possibily related config files.
If GPS is capable of 24 satellites (bcm4751 seems a good GPS chip) simultaneus tracking why only can lock 8 (this is not explainable).
Excuse my poor English.
Click to expand...
Click to collapse
Is it for sure that our Galaxy is using this chip?
I also think that it is an driver problem. while starting gps test at the first moment it locks satelites with signal under 20 snr, but it loose them again and do not lock satelites under 20 snr anymore.
madfarmer said:
Wierd post..
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
May sound wierd for ignorant people who have not been following the story.....
Very sad.....
i havent gone threw every review but any of u guys catch anything in any review?
the epic by far was the best phone ive used but the GPS was down right awful and sprint nor samsung did anything to fix it
XDA fixed it enough to keep me happy. I think people are blowing this gps thing way out of proportion. "If it doesn't work perfectly or, at least as good as other phones then it must be the most awful thing ever!".
Silent25r said:
XDA fixed it enough to keep me happy. I think people are blowing this gps thing way out of proportion. "If it doesn't work perfectly or, at least as good as other phones then it must be the most awful thing ever!".
Click to expand...
Click to collapse
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
imtjnotu said:
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
Click to expand...
Click to collapse
I certainly remember that a lot of people had trouble, but I never did. Mine always locked perfectly and quickly and never gave me trouble on drives short and long.
imtjnotu said:
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
Click to expand...
Click to collapse
I never understood the gps deal. It seemed so sporadic. Mine always worked and I am stock. I used it last weekend on EH17 to drive 5 hours to saint louis and it was perfect the entire way there and back. Didn't cut out once. But you see some people worth working gps and others without it.
Sent from my SPH-D700 using xda premium
I have to agree on the gps sucking. On any drive over an hour I could expect to loose lock. I'd imagine if we looked in some of the other GSII forums we might get a clue.
the only thing i ever loved more about my evo then the epic was the gps....htc never gave me gps issues ever
when i had the bionic or droid x they both locked on quick
Backing up the GPS being just short of useless. Remember, just because YOU haven't experienced the problem doesn't prove there isn't one. On Eclair I had very little trouble, but on FroYo I would constantly lose signal mid-trip, having to frequently turn it off and back on to re-lock and hope I wouldn't lose it right when I was in the middle of complex turns or had missed a turn and needed re-routing. In the Gingerbread leaks it turned to completely useless, locking up 100% after as little as 10 seconds of use, requiring a full restart of the phone to be useful again.
So yes, the Epic's biggest flaw was its next-to-useless GPS, hands down. That said, most reviews of the entire Galaxy S line agreed the GPS was bad on all versions. So far I've heard nothing of the sort about the Galaxy S II phones in Europe which suggests the entire line will be similar, including our new Epic 4G Touches.
imtjnotu said:
was never blown out of proportion.....my girls epic who is stock can never get a lock
mine who was rooted would get signal but never better then 40m lock and would lose signal constantly.....try taking an 9 hour drive with it on and see how many times ur signal is lost
Click to expand...
Click to collapse
If you couldn't fix it then that wasn't the norm. I would have returned it to Sprint and got a different one within the first 30 days.
9 hour drives? No problem. Longest I've been on was 6 but the GPS didn't have any problems. The battery on the other hand...
got mine yesterday, used GPS with google nav and telenav. drove for about an hour in farm country Ohio. GPS took a few seconds longer to lock than my EVo but once locked didn't drop signal. Still a little early to tell but no obvious problems yet.
TurboFool said:
Backing up the GPS being just short of useless. Remember, just because YOU haven't experienced the problem doesn't prove there isn't one. On Eclair I had very little trouble, but on FroYo I would constantly lose signal mid-trip, having to frequently turn it off and back on to re-lock and hope I wouldn't lose it right when I was in the middle of complex turns or had missed a turn and needed re-routing. In the Gingerbread leaks it turned to completely useless, locking up 100% after as little as 10 seconds of use, requiring a full restart of the phone to be useful again.
So yes, the Epic's biggest flaw was its next-to-useless GPS, hands down. That said, most reviews of the entire Galaxy S line agreed the GPS was bad on all versions. So far I've heard nothing of the sort about the Galaxy S II phones in Europe which suggests the entire line will be similar, including our new Epic 4G Touches.
Click to expand...
Click to collapse
Since I don't know who you were responding to I will assume it was me. You know that goes both ways right. Just because YOU have experienced the problem doesn't prove there is one. I have used every official build and every gingerbread leak except EE03 and I have never had a single problem. I use GPS frequently. I have never had a lockup. I have always had an instant lock. And I have always been able to get within 10 meters with the average being 3 meters. However, I never said there wasn't a problem. I just said I never understood the issue as to why it worked for some and not others. You would think that it would be global if the hardware is identical. Makes me wonder if it has anything to do with location in respect to the satellites. Never tried to dig into it because fortunately I didn't have the issue. But I do hope that the touch is without issues because not having gps would be a deal breaker for me.
Sent from my SPH-D700 using xda premium
crawrj said:
Since I don't know who you were responding to I will assume it was me. You know that goes both ways right. Just because YOU have experienced the problem doesn't prove there is one. I have used every official build and every gingerbread leak except EE03 and I have never had a single problem. I use GPS frequently. I have never had a lockup. I have always had an instant lock. And I have always been able to get within 10 meters with the average being 3 meters. However, I never said there wasn't a problem. I just said I never understood the issue as to why it worked for some and not others. You would think that it would be global if the hardware is identical. Makes me wonder if it has anything to do with location in respect to the satellites. Never tried to dig into it because fortunately I didn't have the issue. But I do hope that the touch is without issues because not having gps would be a deal breaker for me.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Just because he experienced the problem means that a problem exists. Whether it's a wide spread problem or a unique incident, the problem still exists. On the Epic forums people are constantly complaining about GPS issues. There are few fortunate ones like you who haven't had the same issues. I didn't have GPS issues for a while until my job had me drive long distances.
cachorropedorro said:
Just because he experienced the problem means that a problem exists. Whether it's a wide spread problem or a unique incident, the problem still exists. On the Epic forums people are constantly complaining about GPS issues. There are few fortunate ones like you who haven't had the same issues. I didn't have GPS issues for a while until my job had me drive long distances.
Click to expand...
Click to collapse
So if you brick your phone because of something you did is the phone bad. Is there a flaw in the phone? No. And again, I never said there wasn't a problem. Actually I said that there was a problem for some and not for others. The only point I was making is that I didn't understand why it worked for some and not others. I wish we could have found the root cause.
Generally speaking GPS on the galaxy S line sucked world wide. Generally speaking it appears that samsung fix this in the galaxy s II.
This is based on reading numerous reviews on both; though it is always possible they messed up on the epic touch as it is slightly different and has wimax; I'm expecting it to work like a charm.
-
I do wonder how many folks who tested gps on the galaxy s remember to ignore wifi triangulation when voicing a comment.
Forgot about this thread and started another a bit further down. I managed to sneak GPS status onto our demo phone yesterday and it locked to 9/10 sats in less than 2 seconds from inside. Accuracy was only at 30m when I cut it off, but it was indoors in a spot where my epic cannot lock at all. Pretty sure it's fixed.
Sent from my SPH-D700 using XDA App
crawrj said:
The only point I was making is that I didn't understand why it worked for some and not others. I wish we could have found the root cause.
Click to expand...
Click to collapse
I did spend a fair amount of time investigating the GPS issues on EC05. There are at least two problems: (i) GpsOne Xtra data that fails to download and update, eventually resulting in stale ephemeris and inability to get timely locks, and (ii) a RIL synchronization bug that results in the GPS crashing with 5% probability on every exit/switch of a GPS utilizing app.
The latter of those two problem is definitely confirmed and affects every EC05 Epic. However, if you only use Navigation once a day, you'll run into that bug an average once a month and might not even notice it. But it is possible to reliably reproduce.
The former of the two problems I never fully understood. The GPS should work as long as you reboot once a week, but we know folks whose phones chronically couldn't download new Xtra data on reboot, likely becuase it was attempting to do so "too quickly" after establishing a network connection. Forcing an Xtra download through GPS Test, GPS Aids, or with a patched framework resolved the issue for most of those folks. The remaining issue is that the ephemeris would still go stale very quickly (hours) on some phones, and an EFS/NVRAM clear appears to help that.
Part of the issue is that the "brokenness" of the GPS is somewhat subjective. It's entirey possible for the GPS to absolutely not be able to get an Xtra-assisted lock, but using almanac data still get one in 30-60s in a vehicle. For some folks, that might be "good enough" and wouldn't think there's much of a problem.
cachorropedorro said:
Just because he experienced the problem means that a problem exists. Whether it's a wide spread problem or a unique incident, the problem still exists. On the Epic forums people are constantly complaining about GPS issues. There are few fortunate ones like you who haven't had the same issues. I didn't have GPS issues for a while until my job had me drive long distances.
Click to expand...
Click to collapse
I think the opposite of what your saying is true. This problem isn't as wide spread as it seems. The few who have this problem are very loud about it and complain about it over the forums. Though I seriously doubt that they are the majority.
If fixing your gps doesn't work then you can always set it back to stock and take it in for repair. If they can't repair and you don't have insurance then you can pay a small fee for a epic with a working gps. I doubt anyone is forcing people to live with a phone that the gps doesn't work on.
Considering that it has a dedicated GPS chip "SiRFstarIV GSD4t GPS" I doubt that we are going to see the same issues.
The integrated GPS on the SoC stinks, and samsung knows that. Using the SiRFstarIV will solve 99% of peoples GPS problems.
engadget claims it is solid. fwiw. http://www.engadget.com/2011/09/15/samsung-epic-4g-touch-review/
Our calls were absolutely solid. The phone's reception is on par with the best handsets around, and we never suffered from dropped calls or degraded quality. Our calls came in absolutely clear, and we think the speakers go to 11 because we had to actually turn down the volume to comfortably hear the other end of the line. The same thing could be said about the loudspeaker for calls and music, which both came out loud and clear without needing to strain our ears or feeling like we needed to break out the headphones. However, the sound seemed a bit limited when watching a full-length blockbuster movie, though we believe this had to do with the quality of the movie itself and not the phone.Last but not least, we double-checked the GPS to make sure it wouldn't have similar concerns to the Galaxy S series, and weren' t disappointed. In several locations -- including a basement next to a window -- the GPS pulled up our location in less than ten seconds. Needless to say, this is definitely a sound improvement, one we imagine had special attention given to it throughout the course of the phone's development.
Click to expand...
Click to collapse
Well, as you can see from the video below, the guy set the highest volume, then place the smartphone near the Galaxy Nexus and the Galaxy Nexus respond to it. This is CLEARLY hardware issues. This could be the real reason Verzion still haven't release the Galaxy Nexus yet.
www.youtube.com/watch?v=BIFRYY25fDo
Thanks dnlsmy.
www.youtube.com/watch?v=y_mO_K7OYR0
Update 1
Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk
Update 2: Lee Johnston explain of "volumegate" issue
Let's talk about the Google Nexus "volumegate" issue.
Today Google said that they have fixed the problem in software, and that a fix is coming.
I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.
I'm a Systems Engineer and also a Developer. I deal with things like this every day.
What we have here is indeed a hardware issue, in that the radio interference is coming in through the radio hardware.
However things like this can be fix fairly easily in software. It's called debounce.
When you monitor an electronic input like the buttons on a phone there is always noise and flutter even when you just press the button. If testing by Google has shown that they just need to turn up the debounce time (the time which an input must exceed for it to be determined to be a genuine press) then it will more than likely just work and no one will ever see ti again.
Like I said I deal with this kind of thing every day, it's not a big deal as long as your debounce time is not excessive. But noise happens down on the order of 1 to 40 ms, real inputs when you press a button last from 100 or 200ms if you tap the button, up to seconds if you hold it down.
This is nothing like Apple and the iPhone 4 antennae problems that could not be fixed in software. I'm sure everyone will see in due time, the problem will be fixed, and the dust will blow over.
And people will be saying "wow, I was wrong, Google rocks
Cheers,
Lee
Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!
Yeah, and for further proof, he does it in the bootloader screen of the GNex
http://www.youtube.com/watch?v=y_mO_K7OYR0
This seems like it's a hardware fault entirely.
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
well you're mistaken then. the test is not inconclusive at all.
martonikaj said:
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
Click to expand...
Click to collapse
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
no software patch can fix this. the phone has inadequate RF shielding.
My bionic which I know is a different device does something similar. When I put it next to my corded work phone and the bionic switches to 4g it causes the speaker on my work phone to male a distortion noise even when it is hung up. So I can see where the radios cause some sort of interference on these 4g phones
Sent from my DROID BIONIC using Tapatalk
TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Would that have anything to do with the nfc chip?
DammitCubs said:
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
please read this post
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
dadsterflip said:
Would that have anything to do with the nfc chip?
Click to expand...
Click to collapse
it has nothing to do with the NFC chip or aerial
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
chandlerweb said:
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
Click to expand...
Click to collapse
yes, exactly - the internal radio on the Galaxy Nexus is causing the problem. that is why those of us who have been affected by this hardware defect have been so vocal about it.
vash1053 said:
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Click to expand...
Click to collapse
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
This is why I effing hate Samsung they always screw something up... Looks like the g-nex us going to be a big failure.. Hint hint goggle you should of stick with HTC to make your nexus line phones
Danrarbc said:
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
Click to expand...
Click to collapse
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
oscillik said:
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
Click to expand...
Click to collapse
Yeah, figured it was. And trying to work around it by analyzing radio signals to detect if it is a real button press or interference would be very hard too, they're going to have to do something about the phones already sold - this is a huge issue.
This is indeed bad. I guess this makes my decision easier about getting one from Hantec. Hopefully the Verizon version doen't have this issue since it uses different frequencies however, this may be the reason they haven't released it yet.
Nexus exchange?
The fact that Samsung have begun replying to peoples comments on their UK Facebook page asking for an email to be sent to technical support including their home address suggest they intend to replace the phone. It`s a great phone and it should never have happened but it`s how Samsung/Google deal with it.
For those who haven’t read the Facebook comment from Samsung :
Samsung UK Hi *, to ensure we investigate thoroughly could you please send the following details to [email protected]: Serial Number, IMEI number, date of purchase, place of purchase, details of issue
your name, address and phone number. We will get in touch as soon as we have more information.
Hello.
Can someone check their compass? Mine doesn't seem to be working (properly)
Testing it with GPS Essentials and Google Skymap, when the phone is parallel to the ground, screen up and turned counter/clockwise, the compass doesn't change at all. In fact the only position it moves when when its in horizontal position with the screen towards me, but even then it doesn't show proper directions..
Here is the video I took how it supposed to work (HTC Inspire 4G on right) and how it actually works.
http://youtu.be/xxxS_HZsRLU
That seems bad! can anybody else confirm please? It will suck to do all the work we r doing for the phone only to have to return them cuz of a bad compass.
Mine ain't all to..reliable. It just goes all over place. If im looking North the damn thing decides to tell me that I'm actually facing South East or something.
First I went outside and tried out skymap and indeed the tracking didn't seem reliable.
I came back inside and installed a compass app: (Compass, by Catch.com).
At first run it asks you to move the phone in a figure 8 to calibrate the magnetic sensor. I did so...Then I got some strange dialog that said "Abnormal magnetic field detected. Please calibrate". While the compass app is running, if I put the phone on a table (or any flat surface) and just turn the phone, the North arrow should stay pointing at north. But on my Nitro it's not!! What's worse is that damned "Abnormal magnetic field detected" keeps coming back.
I tried doing the same thing with my old Nexus One and it works fine, no complaints about "abnormal magnetic field" and when you turn the N1 the North arrow keeps pointing towards north.
This has me VERY worried about this phone!! I noticed the other day that while using the Navigation the software seemed to be locked up (non-responsive when trying to bring up the menu) and if the "abnormal magnetic field" had a play in it, then that would explain it.
---------- Post added at 01:51 AM ---------- Previous post was at 01:32 AM ----------
Also tried installing Sensor Test to see how the other sensors were looking...I didn't even know our Nitro has a Gyroscope! Nice! Would that gyro in any interfere? It shouldn't correct?
Just wondering, n i know it's somewhere on google But I like to tickle all u brainiacs out there to explain wat is the purpose of a gyroscope in a phone. I don't see why we really need it in a phone.
Yeah, if have something like this:
http://www.youtube.com/watch?v=ORcu-c-qnjg
Then apparently it's not working...
If something is really broken in these phones, then I think we all need to reach out to LG and complain or can we have a class action lawsuit against them for selling broken products?
This morning I sent them email regarding the compass issue. Let's see if what they say about it.
But if more people confirm this issue, we could do something about, would need more publicity though.
Publicity is easy enough. Once we get a good amount of people confirming the issue, we can start sending out the story to different forums n tech news sites like engadget, begrudge, gizmodo, n even our beloved xda. Then we can start posting those news on LG's forum n see wat they will say.
We did a similar thing for the atrix before when at&t was throttling back the hspa+ speeds on our phones while iPhone 4 was getting full speed. In months down the road they fixed it.
Sent from my MB860 using XDA App
Here's my suggestion. Everyone with this phone n r having the compass issue with it, please record a video or take pictures/screenshots of how the compass is going haywire. Upload it here, so that when the story hits the news, they can all see that its not just one phone but many. We need to upload as many proves as we can to make a valid statement.
Sent from my MB860 using XDA App
mine shows the sun and a bunch of constellations around it when I pointed at the sun, when I move my phone around it seems to track properly. not sure if that helps
By "properly" do you mean as in HTC Inspire in my video? Or it takes a few seconds after you stopped moving for the image to catch up? - the latter is the best I could achieve after activating GPS and wait for 5 minutes...
I found [email protected]'s thread over at the LG Forums and added my comment as well. Please, anyone else having this issue also post there as that is an official LG Forum.
http://www.lgforum.com/forum/boards/carriers/at-and-t/topics/lg-nitro-hd-compass-doesnt-work
Also, for the Skymap app, there's another potential issue at play...Screen resolution. I tried going into Settings > Display > Screen Optimization and checked-on Google Skymap and that did seem to help the app (redraw was much smoother).
Namuna said:
Also, for the Skymap app, there's another potential issue at play...Screen resolution. I tried going into Settings > Display > Screen Optimization and checked-on Google Skymap and that did seem to help the app (redraw was much smoother).
Click to expand...
Click to collapse
It actually makes sense, since Nitro's resolution is "huge" and not many apps are optimized for such beast.
In fact on HTC Inspire the screen scrolls almost flawlessly in skymap compare to Atrix 4G, with dual core processor, good GPU, but higher screen resolution.
getting interesting lol
I hadn't noticed the compass issue until you guys mentioned it. I did a side by side with an actual compass, and my nitro was nonsense, just all over the place. But actually, when I turned off auto rotate, it fixed it. Check it out on your phone. With screen auto rotate disabled, my compass (and everything else associated, like maps, sky map and compass app) works great, but once enabled, my phone doesn't know it's head from it's ass. Let me know if you guys see the same effect.
It does improve a little on some compass apps, but skypmap sees no difference.
Weird. In that case, my phone is unusual. The compass works pretty well now (for apps including skymap) when compared to my X10 and an Atrix. They're quite similarly accurate.
I wonder if this is just a simple fix we can do ourselves, like maybe updating a file or changing some values in a file. I remember there was a file that we replaced in the Atrix phones to improves its GPS pickup speed and accuracy. I dont know if we can do the same thing here. Let me look for that thread back in the Atrix forum.
It is 20 days since we report a problem with drops after update to 4.0.4 . I judge that it is already too long and we should already have a fix. Now when all customs roms are using a new base, people who have this problem are forced to use an old 4.0.2 because with 4.0.4 phone useless. I think it would be good to start ask Google for any official statement because it is embarrassing for me that that they have such approach to theirs flagship phone.
This thread https://code.google.com/p/android/issues/detail?id=28133 shows that Google has completely no respect to us because there is now prove information that they even try to fix the problem.
Whats a shame Google.
Maybe should we start inform all gadget sites about this behavior?
Hey kid, stop being such a drama queen.
This is not how software development works. It takes time to iron out bugs. It takes time to first find out what causes the bug and then fix the bug and then it takes three times longer than that to make sure that the bug does not cause other bugs in the system.
Let's not forget how long 4.0.4 took to arrive in the first place. They originally released 4.0.3 and then discovered some bugs. Fixing those bugs apparently caused issues in 4.0.4 that no one saw coming, this means that the bug is not easy to find and is difficult to test for. They are doing it as fast as they can.
And let's not forget that not all devices are even affected. I've been on 4.0.4 ever since it was released and I've not experienced a single data drop. So it does not happen with all devices and may be region or carrier-specific. This makes it even more difficult to test for.
you honestly think they are able to push another update to a fix in 20 days?
kara mustafa said:
I judge that it is already too long and we should already have a fix.
Click to expand...
Click to collapse
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?
Just started noticing I have this problem.
I just reboot and it fixes, a hassle, but whatever. reboots pretty fast lol and only happens rarely
luftrofl said:
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?
Click to expand...
Click to collapse
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.
adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
I do?
Same problem here, have to reboot to fix it, any alternative suggestion?
Sent from my Galaxy Nexus using XDA
To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium
luftrofl said:
I do?
Click to expand...
Click to collapse
Lol, he must have misunderstood you.
No, it was a typo and I corrected it.
I meant to say, apparently, you do not. As in, he believes it only takes 20 days to diagnose, text, and implement a fix, which is funny
No fix is diagnosed day 1.
There is time to needed to find the problem.
There is time needed to create a fix.
There is time needed to properly test it, else other bugs show up.
Developers do not work 7 days a week.
Not every Android developer will be assigned to the fix.
There is time needed to ramp up an OTA again in two flavors, ICL53FD_to_IMM76D, and IMM76D_to_whateverthebuildnamewillbe.
Jayrod1980 said:
To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No it does not.
It does not affect CDMA devices, and I have found some GSM users on this forum it does not affect. Folks here just think that XDA is the hub of the world, and therefore if there is a large amount of issues being noted, it must be everyone. Because you know...everyone posts on XDA and other phone geek sites. I am not saying the bug isn't real, just that it isn't happening to EVERYONE.
Theshawty said:
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.
Click to expand...
Click to collapse
It still could be the radios. There is a reason they change radios with each release.
For example, 4.0.4 by itself for CDMA users does not see a signal improvement. 4.0.4 radios on a 4.0.2 or 4.0.3 rom does not see signal improvements. However, 4.0.4 rom and 4.0.4 leaked radio firmware sees a signal improvement.
luftrofl said:
I do?
Click to expand...
Click to collapse
It was a typo, but you knew that.
Theshawty said:
Lol, he must have misunderstood you.
Click to expand...
Click to collapse
reading is difficult..
Some people have reported getting the IMM76I update starting about an hour ago, so for those with the issue, it may help you.
adrynalyne said:
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
He was saying it with sarcasm. You should probably learn what that means before replying.
hotleadsingerguy said:
He was saying it with sarcasm. You should probably learn what that means before replying.
Click to expand...
Click to collapse
He wasn't being sarcastic. Nice try.
luftrofl said:
reading is difficult..
Click to expand...
Click to collapse
Sure is, considering I said several times it was a typo and you still didn't comprehend.