Related
I never get a GPS lock how much ever time I wait, even outdoors. It doesn't work in the latest stock rom also. I tried various GPS fixes from the market but nothing works and I searched the forum too. It used to work properly a year ago. Please help...
Thanks in advance.
vtlrockz said:
I never get a GPS lock how much ever time I wait, even outdoors. It doesn't work in the latest stock rom also. I tried various GPS fixes from the market but nothing works and I searched the forum too. It used to work properly a year ago. Please help...
Thanks in advance.
Click to expand...
Click to collapse
1. Suggestion: Try GPS Status app => free from Play store.
Works fine on my SGS2.
2. Suggestion: Try to flash stock ROM, and do a factory reset/wipe data after flashing. Maybe there is something messed up in your ROM for GPS.
3. Suggestion: If your still on warranty, go the the store/service center and try to get a replacement. Maybe it is a kind of hardware defect.
Good luck !
It_ler said:
3. Suggestion: If your still on warranty, go the the store/service center and try to get a replacement. Maybe it is a kind of hardware defect.
Click to expand...
Click to collapse
Well, it is out of warranty but it worked fine initially. Thanks for the quick reply. Will try the other suggestions...
It_ler said:
1. Suggestion: Try GPS Status app => free from Play store.
Works fine on my SGS2.
2. Suggestion: Try to flash stock ROM, and do a factory reset/wipe data after flashing. Maybe there is something messed up in your ROM for GPS.
3. Suggestion: If your still on warranty, go the the store/service center and try to get a replacement. Maybe it is a kind of hardware defect.
Good luck !
Click to expand...
Click to collapse
Try faster fix from the play store too.
Sent from my GT-P7510 using xda premium
I've started having GPS problems from a few days ago, did the whole flashing to stock then back to my one, re-flashed the kernels, tried faster fix. BUT still no joy, was working absolutely fine until now.
Same for me. Upgrade from lp7 to lpf and now i don't get a fix.
With gps test i even see 11 satellite in view, but don't get a fix.
I tried gps aids to inject xtra data but nothing...
Red_Vex said:
Same for me. Upgrade from lp7 to lpf and now i don't get a fix.
With gps test i even see 11 satellite in view, but don't get a fix.
I tried gps aids to inject xtra data but nothing...
Click to expand...
Click to collapse
http://www.huffingtonpost.com/2012/07/21/sun-solar-flare-sunspot_n_1690576.html
GPS fix and so on won't do anything....
Any of you heard of Google search by the way? Lots of answers there...
LenAsh said:
Any of you heard of Google search by the way? Lots of answers there...
Click to expand...
Click to collapse
NO IM SURE NO ONE HAS EVER HEARD OF GOOGLE EVER.
Anyways, I am in a similar situation and was going to make my own thread but I'll start here.
Been running stock 4.0.3 for a few weeks but wanted to flash touchwiz ux back on because I kind of missed it. So I rooted again and behold, sucked back in to flashing all the new roms I haven't tried.
Problem-and the reason I am posting this to general q&a- is this ; Across all the roms that I flash (slim ics , rootbox, rr 2.6 etc and 3 different custom kernels)- the GPS cannot get a lock.
When I revert back to my nandroid stock 4.0.3 cf root its fine. And TBH I could get a kick out of slim being my daily so I've been searching ask Jeeves and Bing (the only two searches I've ever heard of) and trying many things to no success. Could some one point me to a thread that has helped you if you've had the same problem? Much appreciated.
Sent from my GT-I9100 using Tapatalk 2
i had gps problems when using cm9, but since i flashed sensation rom 3.5, my gps started working again.
so its software based, you could try agps patch
manmad said:
i had gps problems when using cm9, but since i flashed sensation rom 3.5, my gps started working again.
so its software based, you could try agps patch
Click to expand...
Click to collapse
No it isn't - if you look further than the end of your nose, you will realise.
Be a little more circumspect...
manmad said:
i had gps problems when using cm9, but since i flashed sensation rom 3.5, my gps started working again.
so its software based, you could try agps patch
Click to expand...
Click to collapse
Thanks. About to compose a reply in that thread now as I have tried it on all but 1 of the four roms I flashed today with the same results. Both 3.1 versions fail and abort on flash in cwm. 3.0 passes and the problem remains.
Sent from my GT-I9100 using Tapatalk 2
My GPS has miraculously started working again, strange! Solar flare it might have been then by the looks of things?
Hi everybody. I have been reading many of the posts here over the past 6 months and trying to learn as much as I can about different ROMs and issues related to my particular phone which is the Samsung Epic 4G Touch.
Thanks Exit_Only for your helpful work in this thread: http://forum.xda-developers.com/showthread.php?t=1975379. In that thread Sydius 08 asked "How are the Stable 1 tweaks running for you guys? Running CM10 11/18 nightly" I would like to focus on one aspect of that.
First I am currently running cm-10-20121117-UNOFFICIAL-d710 with gapps-jb-20121011-signed. I had installed JellyBeanMod_Stable-One_EO in hopes that it would resolve my long-standing GPS issue. I have read so many threads and I do appreciate all of the comments and attempted fixes by this community. I also use GPS Status and GPS Essentials where I see zero satellites but saw eight or nine instantly with #3 below. Here are the three times when my GPS has worked:
1) When I first got it just over a year ago. It was running Gingerbread 2.3.x (don't remember the last number but think it was 1). It worked perfectly but stopped after about 2 months and worked on and off after that.
2) After the GPS completely stopped working I started learning all I could about using a custom ROM. I tried CyanogenMod 9 but it did not resolve the issue. There's more to the story and more ROMs and tips provided here that I tried but all failed. However, whenever I Odin back to StockCWM-EL26.tar it works perfectly. I followed the tip about getting a fix prior to putting an ICS or JB ROM on.
3) I installed this on 11/15 http://sbrissen.chris41g.org/sbrissen-ALPHA6.zip and my GPS worked perfectly. However, lots of other apps failed miserably and it kept freezing up.
So here I am with nowhere else to turn. This latest CM 10 works perfectly EXCEPT the GPS. I would appreciate any thoughts on this.
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
smoresrock said:
i'm sure someone will mention this, but have you attempted to acquire a GPS lock on a stock ROM, for example, and revert to one of your desired ROMs?
Click to expand...
Click to collapse
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Shlickwilly said:
[ROM]Phantom's Blazer Rom[Yo][8/2/12][v0.1.5][FF18] try this Rom seems to have GPS work in it
Click to expand...
Click to collapse
Thank you. I had actually tried that one and ran into a problem with flashing it but I think that's because I didn't go back to StockCWM-EL26.tar first. I might give it a try again. I do love CM 10 and it would be perfect if the GPS worked.
For those who may not know this guy, QBKing77, is one of the best at teaching how to do this. Here is one for the SGIII and the Blazer ROM which he considers one of his favorites. I had to remove the link because I'm such a newbie. Here is the YouTube description: Blazer Rom on the Samsung Galaxy S III [REVIEW]
allenp007 said:
Thanks for the reply and yes: "whenever I Odin back to StockCWM-EL26.tar it works perfectly."
Click to expand...
Click to collapse
yep. this is the same method i used to fix my friend's GPS issue on a jelly bean ROM. after seeing to it that i was getting a GPS lock on the stock ROM, i went back into recovery, and flashed the ROM she wanted (paranoid android i think it was)... since then, she's been a happy camper locking into 7-9 satellites indoors
Great news! I was able to resolve this issue by following Qbking's YouTube tutorial: "How to Temporary Boot Stock EL29 on the Samsung Epic 4G Touch." I was able to lock on to 9 satellites and get a fix on my exact location. It was literally showing me in front of the building where I was standing.
I hope this helps someone else who might be going through the same problem with their GPS on an E4GT. If someone could post this information and possibly the link to the thread I referenced earlier I would appreciate it.
Thank you everyone for your comments.
Update: nevermind, i just flashed back to the rooted stock rom amd gps is working correctly..i guess i'm done with custom roms..they don't work as well as stock =).
Hey guys, I am currently running the black star xi rom. I'm having trouble getting my gps to lock. I have used the tools available in the system setting to install the att gps config and stock gps config, but both of those don't lock the gps when i running navigation. So, im unable to get voice navigation going. I would have posted this on the black star xi thread...but i don't meet the 10 posts requirement to post there.
simiwizard said:
Update: nevermind, i just flashed back to the rooted stock rom amd gps is working correctly..i guess i'm done with custom roms..they don't work as well as stock =).
Hey guys, I am currently running the black star xi rom. I'm having trouble getting my gps to lock. I have used the tools available in the system setting to install the att gps config and stock gps config, but both of those don't lock the gps when i running navigation. So, im unable to get voice navigation going. I would have posted this on the black star xi thread...but i don't meet the 10 posts requirement to post there.
Click to expand...
Click to collapse
Haven't had any issues with really anything but the new camera not showing on SOA build 3. I was on Padawan v8 which was a really stable and nice and fast rom. No GPS issues ever and do not seem to have any on this new rom I just installed yesterday. Hopefully the official JB will be out soon we'll see.
For some reason none of the AOSP or AOKP ROMs (which sadly is a majority of them) work very well for the Note GPS. The only ROMs I have found with good GPS support for the NOTE have been either Stock ROMs or custom ROMs which were derived from a Stock ROM.
d00mz said:
For some reason none of the AOSP or AOKP ROMs (which sadly is a majority of them) work very well for the Note GPS. The only ROMs I have found with good GPS support for the NOTE have been either Stock ROMs or custom ROMs which were derived from a Stock ROM.
Click to expand...
Click to collapse
Good to know. Which is why I guess Padawan v8 was so stable for me. Thanks for that info.
Demmonnixx said:
Good to know. Which is why I guess Padawan v8 was so stable for me. Thanks for that info.
Click to expand...
Click to collapse
Honestly it kills me too. I LOVE the new features on ROMs like JellyBeer and other CyanogenMod types, but I'm a nerd and use GPS everyday, and it keeps pushing me back to the other ROMs for the GPS performance.
d00mz said:
Honestly it kills me too. I LOVE the new features on ROMs like JellyBeer and other CyanogenMod types, but I'm a nerd and use GPS everyday, and it keeps pushing me back to the other ROMs for the GPS performance.
Click to expand...
Click to collapse
I understand that. Probably fixing to switch back to Padawan v8 if I cannot get the new camera options to work properly in SOA build 3.
Well idk if i should ask here or put a new thread sorry im such a noob! But i have the same problem but with ebery singls rom at this point! Even stock. Ive tried flashing radios, gps test apps to remove agps data, and almost every fix i could find but none work! I even flash from rom to rom the weurd thing is its just navigationaps can locate me easily as well as any app needing my location. Help? Please and thank you.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
carol7611 said:
Well idk if i should ask here or put a new thread sorry im such a noob! But i have the same problem but with ebery singls rom at this point! Even stock. Ive tried flashing radios, gps test apps to remove agps data, and almost every fix i could find but none work! I even flash from rom to rom the weurd thing is its just navigationaps can locate me easily as well as any app needing my location. Help? Please and thank you.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Maybe start by reposting your issue so others can understand it. If I understand what you wrote, you have the same problem but your navigation apps locate you easily. And that doesn't make sense. Are you trying your GPS outside??
Srry i type fast n misspelle loll (idk how to spell misspelle) okay so wat i meant was that the only app that just keeps sayin "searchin for gps" is the navigation app. The maps app pinpoints my location easily as dies fb n any other app requesting my location. Ive tried every fix i could find on the web and nothing has worked for me! Ive seen fixes with flashing a stock gb radio it didnt work. The gps test app fix didnt work. Ive flashed countless roms from gb to jb n still same issue. N yes im outside ive even been on the roof! (seriously ive been up there am terrified of heiqhts n was stuck for hours didnt think it throuqh lol) thnx for any help.
「¡sent from my phone cuz its better than my computer!」
---------- Post added at 09:10 PM ---------- Previous post was at 08:14 PM ----------
So I finally got it to work I actually just pryed up the antennas a little bit just so that they would make contact with a top antennas as well I just thought I'd let you guys know in case you guys ever came across this problem as well thanks for all your help!
「¡sent from my phone cuz its better than my computer!」
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
Hi,
Search everywhere and still stuck!
This is issue that I have bee trying to solve on the 'android-rsap' forum, but am completely stuck, so by posting here I am hoping that someone can shed some light on what is going on.
Link: forum.android-rsap.com/viewtopic.php?f=32&t=871
In short, the device is a Samsung Galaxy 2 (XEU), and the bluetooth rsap functionality works fine with 4.0.4 (I9100XWLPT) but when I upgrade to 4.1.2 (I9100XWLSW) it no longer works at all. What is most weird is that it seems to be only my handset that is affected, it does not seem to be a universal issue. :roll eyes: What could be specific to my handset that stops this functionality working as it should?
I have been going back to 4.0.4 and upgraded to 4.1.2. many times now, via OTA, Kies and Odin, same result every time, sadly. 4.0.4 works every time, 4.1.2 has never worked with rsap and my car
What could be specific to my handset that stops this functionality working as it should? I have tried root'ing the handset to do more testing and to try the rsap app from Google App Store, but that has the same issue. Could some of the radio software be wrong? or?
Picture shows Kies upgrade screen and the 4.0.4 and 4.1.2 versions I am getting.
Any hints would be appreciated.
Regards,
J.
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
gastonw said:
Try another JB ROM, and stop going back to 4.0.4.
Sent from the little guy
Click to expand...
Click to collapse
Ok, so with an XEU handset - what version would you recommend?
realist42 said:
Ok, so with an XEU handset - what version would you recommend?
Click to expand...
Click to collapse
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
..
realist42 said:
Ok, So I am a beginner with hacking my Samsung phone, this is mainly as I use them as phones, and want to rely on them. Before I had encountered this issue I had not even rooted my phone before.
I would really appreciate some help with this, this is an issue what is well beyond me, as in my view, what I have done ought to have fixed it. If there was a firmware issue, my reload should have but it back to 'factory default' .
As for going back to 4.0.4, well it works, so it must be a baseline for something, it proves the radio and bluetooth stack is capable of doing the right thing.
I think I need some pointer of getting my had set back to completely stock PDA / CSC / PIT, but don't know how to do it, or where to get the parts, to date got the firmwares from SamMobile... Any help would be appreciated.
Regards,
J.
Click to expand...
Click to collapse
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
king_below_my_lord said:
The firmware specified by Kies (the one in the picture you posted) is your region specific firmware, just search and download the firmware from sammobile and flash it if you want to go back to stock, gastonw was suggesting you to try a different version of jb like xwlss, xwlsn, xwlsw, etc... If it's common to other jb versions then probably Samsung removed proper support for it, it's not the first time they have done it, like for example they completely removed action shot feature in stock camera in jb(this is there in ics).
Edit:If this problem is specific only for your s2, you might have to try flashing different firmware.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
realist42 said:
Thanks,
I have tried a completely different firmware, and it behaved just the same. The odd thing is that there are no other reports of users having issues with the rsap application on a S2 with JB, so the support is on there (the app provides the stack if it is missing), but the app does not work either so it looks like it is my handset that has issues. I just can't figure out what to do to fix it. There is one thing that could be at play here, I did have a flailed upgrade from GB to ICS (4.0.3) where vibrate stopped working. It was sent to Samsung for repair, not sure what they did but I suspect that the just flashed the phone with a new version of the same firmware. Could there be something there that still causes issues?
Thanks.
J.
Click to expand...
Click to collapse
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Repporte Redan
king_below_my_lord said:
Hmm try generating a logcat when you try to use that feature and post it here, let's see whether some useful report is generated , please generate it as quickly as you can after you try activating/using that feature.
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
HI,
Took a little time to get the phone back in order and then to go an do the trace.
Not knowing what I am really looking for, but it strikes me that the bluetooth stack looks to just be giving up...
Regards,
J.
Hi all,
Well, today I managers to briefly borrow another S2 handset with JB on it. This other handset has the same issues that I have, so this must be something in the packaging of the Bluetooth that Samsung did - but I am guessing here.
Any clues would be appreciated, although I think I am fighting a loosing battle here... (works with an S3, so I should go and upgrade! at least chapter now that there is the S4 - but I like the form factor of the S2 better)
Regards,
J
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
king_below_my_lord said:
I can't find anything that can cause a reasonable problem in your logcat, since you tried it out with an other GT-I9100 running JB and reproduced the problem, my guess is as good as yours.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Well, thanks for looking anyway...
My thinking on this is now that as it works with newer cars and only the older ones that now have issues, it must be a version issue, i.e. the version of the bluetooth stack is not the one it should be. It would be interesting to know if there is a difference in the version of the bluetooth stack and the rsap daemon between the S3 (which works on JB) and the S2 (which does not). Would that tell me anything interesting?
Regards,
J.
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
djshotty said:
Your issue is directly related to 4.1.2 (and newer) versions of Android having changes to what's known as a2dp, or Advanced Audio Distribution Profile. Supposedly, these failings with Bluetooth connectivity of our blessed i9100 are fixed in Android 4.2.2, but unfortunately this version has not yet been released for it (and before anyone says otherwise, I dare them to show me where I can get the ridgey didge true blue real deal Jellybean 4.2.2 for the i9100, especially when sammobiles - the number one place for Samsung firmwares - don't have it for any country on the planet)
Click to expand...
Click to collapse
HI,
I was not aware of this, and are you saying this is specific to the S2, so the fact that is works with an S3 on 4.1.2 is irrelevant?
J.
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
djshotty said:
well, I've been researching this since 4.1.2 came out, and it isn't an issue only experienced here in Australia. Google is a great resource, go for a surf and you'll find out more...
Click to expand...
Click to collapse
Well, my issues are with specifically with rsap, not really A2DP, but if it affects the whole stack, this could be an issue.
To illustrate: I have 2 cars, one older, one newer. With the newer car all is well, and it works at is should (as far as I know) The older car was working pretty much with out issues on 4.0.4, but refuses to work with 4.1.2. Both cars rely on rsap.
Not sure this helps, just wanted to illustrate the problem that I am trying to solve.
Regards,
J.
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
djshotty said:
Have a look at what people are talking about in a Google discussion group, about this very issue...
Code:
http://code.google.com/p/android/issues/detail?id=41628
Click to expand...
Click to collapse
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
realist42 said:
Maybe I am overly cautious here, but in my case it works just as it should with an S3, no issues at all, for me it is the S2 with JB that has the issue. And the functionality that does not work does not go near the A2DP libraries as the phone becomes a bluetooth SIM card for the car to access (which is rsap)
There must be others out there that also have this issue?!?
Click to expand...
Click to collapse
That's why I suggested you look at the forum I provided the link for, there are plenty with the 'Phone calls via Bluetooth into car stereo' issue, including myself...