Greetings fellow Galaxyenz,
I have a Galaxy S that worked all ok with JF5 stock ROM, paired with my car for phone audio, using bluetooth. Never had a disconnect...
Then I applied the procedure in order to get the HackEclair ROM 1.0.4 (flashed JM5 through ODIN, then recovery and applied update.zip). After that, i applied OneClickLagFix 2.0.
##EDIT## I'm currently on JM7 + Tayutama rom and it still exists.....
At the end my phone flies like a Concord, and it performs 2200 on Quadrant =)
My only problem right now is that Bluetooth connections to the Car audio, only last for 30 seconds.
I have to completely disable and enable Bluetooth on the phone in order to get the audio working again... for 30 more seconds... =(
Although the phone rocks with this ROM, having no bluetooth system in the car because of this ROM, is a no-go for me.
Thanks for you time. This forum has a great helping initiative.. It's precious, let's keep it
Cheers
Phk
EDIT -- Developed a dirty fix. Works OK for me now!
Just to make this thread complete, i've found the bug is related to some configuration desynchronization between car and mobile.
So android bt stack must be reseted.
I've developed my first app for this, so that i can reset confs with one click
thanks to every1 at XDA, you guys rock =)
http://www.multiupload.com/KI0WJ2RKZB or Check attached!
Cheers,
Phk
Good work! Finaly someone fixing stuff on own. You sir are all class
Sent from my GT-I9000 using Tapatalk
Word!
10cc
miki4242 said:
Word!
10cc
Click to expand...
Click to collapse
Thanks miki
The app is now on the Market, and i've realized that my car picks up the device faster if it has a new name after the fix, so i will implement a random "Android-XXXX" name for each time you click "Fix" =)
Install it from the Market to make sure you receive updates.
I'll also try to perform these steps, as they as what i really to:
- turn off bluetooth
- run this apk
- press fix
- turn on bluetooth
- change name
- reboot
Cheers!
Cool to see you addressing this with your own fix, but JM5 did have buggy BT with my car as well. Never a problem with JM6, JH1 or JM7. Maybe the better fix is to just get one of those firmwares, which don't have the problem you describe, and also drastically improve GPS (really, they do - for me anyways) and also are much less "laggy" even without fixes.
Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there That's why i've built up the tool, i have to use it every 2 days (more or less)
Anyway thanks for the thumbs up! =)
Cheers
Phk said:
Hey distorted... Sorry to disappoint you, but I have JM7, and yes, the problem is still there That's why i've built up the tool, i have to use it every 2 days (more or less)
Anyway thanks for the thumbs up! =)
Cheers
Click to expand...
Click to collapse
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.
Perhaps you should rename the thread, then, if it's not specific to JM5.
Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.
And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?
Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).
distortedloop said:
Disappoint me? LOL, not at all. I don't have the problem since moving on to newer leaked firmwares than JM5. I definitely had the problem on JM5, though.
Perhaps you should rename the thread, then, if it's not specific to JM5.
Additionally, your OP says nothing about different firmwares other than no problem on JF, but the problem on JM5, maybe you should include that the issue is there on JM7 also.
And finally, if you're still running RyanZA's lagfix, and/or the HackEclair ROM, how do you know they're not the real root of your BT problems?
Coincidentally, I was also on OCLF hack and JM5 when I had BT problems. Maybe it's the OCLF that's the problem, since I am on JM7 and don't use OCLF any more, and don't have the problem, but you do(?).
Click to expand...
Click to collapse
Yes, i might change the thread name
I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...
Phk said:
Yes, i might change the thread name
I'm on JM7 now with OCLF, but there's absolutely no reason for OCLF being the root of the problem.. Have you checked the full source code? I've read it line by line...
Click to expand...
Click to collapse
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.
Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:
Me: JM5 + OCLF = buggy BT
Me: JH1 + voodoo = working BT
Me: JM7 + voodoo = working BT
You: JF3 + nothing = working BT
You: JM5 + Hackclair + OCLF = buggy BT
You: JM7 + OCLF (+ Hackclair??) = buggy BT
The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.
It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).
With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.
Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.
The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.
All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help!
distortedloop said:
Full source code? Do you mean the scripts it runs? Of course I have. I manually ran them one by one to install OCLF on my phone since the batch doesn't work on Macs, and I generally want to know what exactly some script is doing to my phone in case I have to undo the steps if the script borks my phone.
Perhaps there's no reason OCLF (or Hackclair) would cause this problem, but lets look at the little bit of known data we have between the two of us:
Me: JM5 + OCLF = buggy BT
Me: JH1 + voodoo = working BT
Me: JM7 + voodoo = working BT
You: JF3 + nothing = working BT
You: JM5 + Hackclair + OCLF = buggy BT
You: JM7 + OCLF (+ Hackclair??) = buggy BT
The only common elements to EVERY scenario that has buggy BT that we have specifics to so far include OCLF.
It seems perfectly reasonable to assume that OCLF (and/or Hackclair if you're running it in your current buggy BT configuration) are part of the problem (edit: unless of course you just have buggy hardware).
With that in mind, a reasonable troubleshooting step would be to uninstall both OCLF and Hacklair and see if you have issues on stock JM7. If you don't, then we know that one of those modifications are the problem.
Since you've found for you what is an acceptable workaround, it's probably more effort than you're interested in doing to test that out, and I'm not interested in breaking what is a perfectly working combination of firmware/lagfix on my phone to install OCLF to test it out, so we'll probably have to rely on others reporting their configurations that work or don't work.
The only technical reason I might suspect OCLF as the issue is that in my experience, and the reports of others I've read, OCLF starts to lag again after a day or two of uptime on the phone. What if the BT disconnects are related to the system lagging? It's a stretch, I know, but I can't ignore the fact that between the two of us, the only thing we had in common while experiencing BT issues is OCLF. That's significant, in my humble opinion.
All that said, if I start experiencing BT problems out of the blue on any future configuration, I'll certainly look to your app for help!
Click to expand...
Click to collapse
Thanks man Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.
About the code: I was refering to OCLF source code (GPLv3) of the Market App
About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question
Anyway, you are right, there is a common name: OCLF.
I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?
Phk said:
Thanks man Useful post! I've spoken to RyanZa before implementing this app, to confirm that there were no possible misunderstandings.
About the code: I was refering to OCLF source code (GPLv3) of the Market App
About the lag returning: I reboot my mobile frequently so the 2 day lag-reappear is not the question
Anyway, you are right, there is a common name: OCLF.
I might test this BT with Voodoo. What are the downsides of voodoo vs oclf? oclf is very neat and clean you know... ?
Click to expand...
Click to collapse
I don't imagine the apk for OCLF does anything different than the scripts do, essentially make the large data file and then loop mount it. So the end result is surely the same.
I don't really want to pollute this thread with the merits of OCLF vs voodoo, some people get a bit to "religious" or defensive about it and the thread will devolve to being really off-topic if that happens. There are plenty of threads hashing that debate out.
Personally, I think voodoo to be nice and clean as well. Voodoo requires a custom kernel and you install it via Odin. It backs up your data, formats /data as ext4, then restores the data it backed up to it. Simple, clean, reliable, but not as simple as just running an app from the Market. (For the record, Ryan, I'm not saying here that your method isn't reliable. )
The primary disadvantage for you to test it out at this point is that the beta1 is no longer available publicly, and the beta2 won't be released until "sometime this week", so really not easy for you to test out.
I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.
When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.
I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day. I never ran JM6/JM7 without OCLF though, so this may not be related at all.
Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).
Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.
PlanetJumble said:
I am experiencing problems with a Bluetooth car kit as well, but different. Every now and then, the connection hangs. The stereo isn't receiving anything, but displays connection status for phone and media. The Galaxy S displays connection as well, the music player looks like it is working, but no sound can be heard.
When I turn off Bluetooth on my car kit, the Galaxy S still displays connected status. Turning off via status bar shortcut or settings menu makes it stay in "turning off" mode indefinitely. Sometimes I can't even bring down the status bar. And even shutting down the device doesn't work, as it is not completely powered down, I have to force it (10 seconds reset button) anyway. Then boot up and hope it doesn't happen again right away.
I had that problem with JM6 + OCLF and still on JM7 + OCLF, but as far as I can remember, it didn't happen on JF3, where I had OCLF running for quite a while as well. And I use my car kit every working day.
Getting off topic now, but I noticed something else with OCLF: when it is applied, and I connect the USB cable, it locks the internal and external SD cards even when in menu mode without choosing "mass storage". In that state, I can't access them neither from the PC nor from the phone. I need to select "mass storage" then disable it again (already put it as default because of that), which is also pretty annoying because my car charger does fake a PC connection (probably because some devices won't charge otherwise).
Before OCLF, I could just ignore the popup menu for USB mode. I am just saying that, because it is another side effect of OCLF which can hardly be explained by looking at the source.
Click to expand...
Click to collapse
Wow, that's a totally uncommon behaviour from SGS!
How do you flash it? Do you use CSC+MODEM+PDA? Re-Partition?
Cheers, good luck!
Phk said:
Do you use CSC+MODEM+PDA? Re-Partition?
Click to expand...
Click to collapse
Yes, on both updates, all in one step.
But the strange USB behaviour was already present with factory firmware JF3 (after OCLF).
BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.
PlanetJumble said:
BTW: the Bluetooth problem doesn't happen very often, between once and three times a week I'd say.
Click to expand...
Click to collapse
Yes, same as me. I have to use the fixer to restore connectivity... :\
About the USB, change your SGS using warranty....
Phk said:
About the USB, change your SGS using warranty....
Click to expand...
Click to collapse
I don't think so.
BTW: I moved from OCLF over to Voodoo (and to JM8). And it did solve nearly all problems. Bluetooth never crashed since (also didn't in a few days of Voodoo on JM7). Also now USB connection doesn't automatically lock the SD cards anymore.
And I noticed something else: OCLF prevents fonts from being rendered bold on certain web pages like Google Reader. Missed that before but I thought maybe Google removed the bold fonts to save space. I like it better with bold fonts though, glad to have them back.
Ongoing BT and OCLF Issues...?
Not sure if this is relevant, but I'll post anyway just in case it is and it gives someone else a eureka moment.
I'm on a stock Eclair ROM - JM2, I know, I've re-flashed it several times now...! - and have had no end of troubles with some combination of root, OCLF and/or the other XDA kernel mods that come with OCLF. I've ruled out the last of these by not changing scheduling or anything else from defaults; I doubt it's the first of them because I've tried a couple of different root methods. So it's probably OCLF itself, I just don't have the appetite yet to re-install everything only to screw it up again "to see if" ...
Anyway, rSAP carkit - pair, connect, everything is fine. Install OCLF, and within a day or two (and *perhaps* related to having to remove/reinitiate the ext2 partition because of the Kies sync issues), I get:
1. Carkit unable to see the 'phone at all (rare, may be unrelated)
2. Carkit sees, connects, but tells me there's no signal (dashboard shows blank signal bars, RNS510/Columbus head unit tells me there's no network) - but I can still make calls
3. Carkit sees, connects, but tells me there's no signal as above but genuinely means it: any attempt at calling gives a network error (most common)
4. Carkit and 'phone won't disconnect properly, so the 'phone is locked out of the network until you reboot it (rSAP borrows the SIM identity of the 'phone for the car, so if it doesn't give it back then the 'phone can't reconnect to the network - the handset thinks it has no SIM card). (every time)
I'm just rebuilding the handset (again) without any mods to see if the problem goes away, but I can't imagine it's related to any other application that I have installed.
Pity me and my poor, laggy handset.... if I find out more, I'll report back. I might have a look at the BT fix posted here (thanks in advance!) to see if that helps if the problem does reoccur... or try Voodoo, so long as I can do it without my wife spotting that I'm in the process of breaking that very expensive 'phone again
Related
In the recent cyanogen roms since 4.19 which required flashing with the htc radio my gps has stopped getting fixes. I am limited to only cell tower location. Maybe this is a radio issue? If so what is the best radio alternative which will work with cyanogen roms? I need my gps back. Thanks.
I just tested gps on my dream with cyan 4.2.1 on top of the htc flash. Working with no problems, even indoors. If you don't get any better tips, I would suggest installing again, and this time wipe ext3 partition in addition to wiping, and don't restore anything from backup for root users etc. before you check the GPS.
Hi
This may not be a tip, but i had the same problems when i upgraded rom, I had copilot and Ndive that worked prior, But stopped after urgrading rom to CYAN 4.1.999
Only solution i found was to try other alternatives, the only one i got to work flawlessly was Sygic mobile maps 9 V7.71, gets a fix almost immediatley and works Perfecto.
Hope this helps
I have the exact same problem!
I flashed cyan 4.21 and stopped getting GPS fix. I wiped, wiped ext3 and installed enomther AOSP 1.6 without the expansion pack. I can't get a gps fix anyway...
axlastro said:
I flashed cyan 4.21 and stopped getting GPS fix. I wiped, wiped ext3 and installed enomther AOSP 1.6 without the expansion pack. I can't get a gps fix anyway... What the hell did cyan do this time. He really messes up basic functionality on android, I think that's why google are trying to stop him.
Click to expand...
Click to collapse
Christ, thats an ignorant post
Cyanogen does not "mess up basic functionality", 99.9% of people running his roms have no such problems, myself included. It was probably something you missed or did wrong in the process. Did you follow the steps in his first post carefully, it is a more convoluted process coming from 4.1.11 because of the changes required by Google. In any case, rooting and installing custom roms has its risks and you chose to accept those risks, stop trying to blame someone else when it goes wrong. Take some responsibility, be constructive and try to find a solution instead of crying about it.
Incidentally, the reason Google had an issue with cyanogen was, completely legitimately, because his roms included some of their closed source apps (mail, youtube, market etc) hence why his new roms do not include those and Google are fine with him now. Try reading about it before you shoot your mouth off
I'm trying to work out the problem right now. I wiped again and installed another rom - not cyanogen. The problem is still here. It seems to be a problem that not only I have. It's quite possible that I, and others having the same issue, haven't followed the instructions correctly or did something else wrong.
Try flashing the radio
http://android-roms.googlecode.com/files/ota-radio-2_22_19_26I.zip
Well, seeing as my GPS just got a fix indoors with Cyanogen's 4.2.2, I think the problem is with you.
Now, without posting what you have done to get your phone to the state it is in now, how in the world can we help figure out what went wrong? This really seems like an isolated incident, and obviously not one that is suggestive of Cyanogen's rom being faulty (pretty damn insulting of you to blame him) since you have the problem even after flashing a rom that you give so much praise to for being 'stable'.
So..... how about you reconsider what you might have done to your phone, and try some troubleshooting...
1. When I am having issues with my GPS, sometimes I find it helps to disable GPS (both wireless and sat), reboot my phone, re-enable them, and try again to get a fix.
2. Use GPS Status2 to see if it is connecting to any sats at all.
See what happens... Who knows, maybe there is something wrong with your phone (ever imagine that?).
Not trying to be rude, or bash you, but you were pretty rude and bashing towards Cyanogen, and then you said you had the problem with someone else's rom too...
daveid said:
Well, seeing as my GPS just got a fix indoors with Cyanogen's 4.2.2, I think the problem is with you.
Now, without posting what you have done to get your phone to the state it is in now, how in the world can we help figure out what went wrong? This really seems like an isolated incident, and obviously not one that is suggestive of Cyanogen's rom being faulty (pretty damn insulting of you to blame him) since you have the problem even after flashing a rom that you give so much praise to for being 'stable'.
So..... how about you reconsider what you might have done to your phone, and try some troubleshooting...
1. When I am having issues with my GPS, sometimes I find it helps to disable GPS (both wireless and sat), reboot my phone, re-enable them, and try again to get a fix.
2. Use GPS Status2 to see if it is connecting to any sats at all.
See what happens... Who knows, maybe there is something wrong with your phone (ever imagine that?).
Not trying to be rude, or bash you, but you were pretty rude and bashing towards Cyanogen, and then you said you had the problem with someone else's rom too...
Click to expand...
Click to collapse
First off. I have tried both steps you suggested.
With gps status I can see 4-5 satelites and the lower right of the display says 0 sats. So I can't get fix, the gps itself works. Could be a problem with gps.cfg, I'm going to look at it now.
The issue occured right after I flashed cyanogen 4.2.1 stable. Even afer wiping entirely and flashing another rom I have the same issue, So I suppose that that the problem might be radio related. I actually consider there might be a problem with the phone, but a user who started this thread also had similar problem after going to cyanogen build. Maybe he did the same mistake as I did. Many times I have installed roms and had no issues while others had them - sometimes they occur sometimes they dont - depending on what spl/radio you are on, even what network you are on and what ROM you are coming from. Sorry for being that rude, I realize that now...
axlastro said:
First off. I have tried both steps you suggested.
With gps status I can see 4-5 satelites and the lower right of the display says 0 sats. So I can't get fix, the gps itself works. Could be a problem with gps.cfg, I'm going to look at it now.
The issue occured right after I flashed cyanogen 4.2.1 stable. Even afer wiping entirely and flashing another rom I have the same issue, So I suppose that that the problem might be radio related. I actually consider there might be a problem with the phone, but a user who started this thread also had similar problem after going to cyanogen build. Maybe he did the same mistake as I did. Many times I have installed roms and had no issues while others had them - sometimes they occur sometimes they dont - depending on what spl/radio you are on, even what network you are on and what ROM you are coming from. Serry for being that rude, I realize that now...
Click to expand...
Click to collapse
We all get upset when things don't work that we expect to, my suggestion about that is to go back and clean up your posts before Cyanogen reads them (hopefully) so as to avoid pissing him off.. He has given us so much, and we don't want to alienate him on XDA...
Anyway, about seeing satellites but not getting a fix, have you tried re-flashing the radio?
You said you have wiped, and flashed two different ROMS. The possibility of it still being a software issue are slim (but still there), if the radio doesn't help... it just may be a hardware thing.
I have never had mine get locks on satellites and not lock-in my position.
I know this stuff has been mentioned, but here is your basic troubleshooting process. Complicated, I know. Shouldn't take all day.
Download GPSStatus2 from the market and check to see if it is connecting to any satellites at all.
a) Go outside, away from buildings and trees, and open GPSStatus2. If it connects to 1 satellite, your receiver is working and it's probably some fluke of atmospheric interference (rain, dust, clouds, temperature, vapor, fog all affect microwave transmission; even air quality) that it can't connect to more. Try some different areas with different weather.
b) If it connects to zero, reinstall radio image from the link a few posts up.
c) Still no luck, go all the way back to stock firmware (flash OriginalSPL if you have DangerSPL installed, then RC29) and let it update to Donut, try again.
d) If it's still not working, your GPS happened to randomly die or something. Call T-Mobile cause you need a warranty replacement. They will send you a new phone, you send the old one back.
You know... if you are only trying google maps, try downloading some alternatives. One off the top of my head is RMaps.
I'm flashing the radio now. I have tried the other steps. I tried to get a fix from different locations, now I'm in the mountains and the device has a clear view to the north, where most sattelites are supposed to be... Yes it could be a hardware issue. As you can see another userr ATINsa, who started the topic has the same issue.
still problems
I don't know why you are attacking that guy. There is a problem. I had it on my old dream which was just stolen and replaced. And now I have it with the replacement. Prior to 4.19 and the radio you had to flash to keep cyan cool with google I had no problems. Google tracks, my maps editor, and google maps have a problem. When using wifi can sometimes connect more. The old cyan roms worked fined. Please don't try to explain to me how to use a gps. I have reflashed and redormatted. This has reccured with all roms since I had to replacwe the radio with the one required for him to be cool with google.
So the quesstion is, what other radios are the newest and will work with gps and cyanogens newest rom?
There are 2 people in this thread with the same prob. A third says google maps didn't work but anothewr gps program did. I have experianced this with2 googlde dev dreams. There is a problem and its not a user problem.
Something like this really sounds like a hardware issue. I don't mess around with the GPS code in my ROMs.
AntiNSA said:
I don't know why you are attacking that guy. There is a problem. I had it on my old dream which was just stolen and replaced. And now I have it with the replacement. Prior to 4.19 and the radio you had to flash to keep cyan cool with google I had no problems. Google tracks, my maps editor, and google maps have a problem. When using wifi can sometimes connect more. The old cyan roms worked fined. Please don't try to explain to me how to use a gps. I have reflashed and redormatted. This has reccured with all roms since I had to replacwe the radio with the one required for him to be cool with google.
So the quesstion is, what other radios are the newest and will work with gps and cyanogens newest rom?
There are 2 people in this thread with the same prob. A third says google maps didn't work but anothewr gps program did. I have experianced this with2 googlde dev dreams. There is a problem and its not a user problem.
Click to expand...
Click to collapse
The thing is, the radio that is flashed with the HTC system image, should be the same radio that you were already running on your phone. I don't think that has been changed since 1.5 came out.
And the problem with your theory of this being more than just an isolated incident is this: most people aren't experiencing this problem, only a handful (two or three people here or there does not a system problem make).
I'm 26 years old and have had windows mobile devices and now I've been on android for about half an year. I have used linux back in school when most of the kids here, blindly defending cyanogen were toddlers. I didn't mean to attack cyanogen or whoever else. It's just that the problem is with at least 2 or 3 people and maybe more. The right thing to do is to calm down and try to go back to a state which works. I have reflashed radio and gone to AOSP donut build. Still no luck. When you wipe you wipe /data and /cache right? What about /system ? I bet it's some of the libraries that have something to do with controlling GPS hardware, which remains after a wipe. It would be a nice idea to flash the SPL again. It will probaby clean things up. This is the next thing I'm going to try. It's a good time for someone with better knowledge of how android works step up and give any other ideas.
For now try :
Flash SPL again (whatever SPL you are using)
Flash Radio (latest one from htc developer site)
Flash some basic rom, like TMO cupcake or donut and let's see of it works. That's what I'm trying to do now. If this doesn't help, we might try the proposed reverting to stock spl and RC29.
axlastro said:
I'm 26 years old and have had windows mobile devices and now I've been on android for about half an year. I have used linux back in school when most of the kids here, blindly defending cyanogen were toddlers. I didn't mean to attack cyanogen or whoever else. It's just that the problem is with at least 2 or 3 people and maybe more. The right thing to do is to calm down and try to go back to a state which works. I have reflashed radio and gone to AOSP donut build. Still no luck. When you wipe you wipe /data and /cache right? What about /system ? I bet it's some of the libraries that have something to do with controlling GPS hardware, which remains after a wipe. It would be a nice idea to flash the SPL again. It will probaby clean things up. This is the next thing I'm going to try. It's a good time for someone with better knowledge of how android works step up and give any other ideas.
For now try :
Flash SPL again (whatever SPL you are using)
Flash Radio (latest one from htc developer site)
Flash some basic rom, like TMO cupcake or donut and let's see of it works. That's what I'm trying to do now. If this doesn't help, we might try the proposed reverting to stock spl and RC29.
Click to expand...
Click to collapse
If you wipe it wipes /data, if you flash a new rom it "wipes" (it really formats) /system and /cache. Nothing is left behind on /system...
Ok. I fixed the issue. I'm on danger SPL , newest radio etc...
I reflashed radio (as adviced above). Prior reflashing the radio wiped and installed enomther AOSP+ADP 1.6, with exp pack 2.11.
After that installed an app from market called GPS TEST (Don't know if it had something to do with GPS being fixed)
It detected 5 satelites right by the window indoors. Then Google maps found my location.
axlastro said:
I'm trying to work out the problem right now. I wiped again and installed another rom - not cyanogen. The problem is still here. It seems to be a problem that not only I have. It's quite possible that I, and others having the same issue, haven't followed the instructions correctly or did something else wrong.
Click to expand...
Click to collapse
well if you tried another rom and its still there .. then the problem might lie with your phone and not the roms you installing .... is anyone else around you with a G1 not getting gps location also ?
Android so far as far as I can determine does NOT support using a Bluetooth GPS for the location data but I'm hoping maybe Froyo does..
The GPS built into phones is fine for car nav and some low-resolution stuff, but to have any accuracy or hold a decent lock under heavy foliage or urban jungles a bluetooth GPS with a dedicated chipset is necessary.
I geocache a lot, and my Holux 236 has never failed me, it always has lead me right to where a geocache is, yet my Nexus One tonight the heading and distance stuck, stuttered, seemed to be 20+ feet off at times, and almost IMMEDIATELY went stupid after going under foliage.
I've seen a few programs that'll use Bluetooth GPS themselves, but they are one-off programs which use the GPS directly, not replace the internal GPS data with the Bluetooth GPS data which is what I really need.
Anyone with Froyo and a bluetooth GPS?
i would like to know to
The answer was no... Still an open issue, probably will remain an open issue.
http://code.google.com/p/android/issues/detail?id=9057
Looks like there's maybe two possibilities, one open-ended "I have solved this" with no real info, and another "Bluetooth GPS Mouse" app in market that is said to work. I'm going to try.
So far this seems to work! I've got an email out to the author, I'll post some more on it soon.
Pretty slick the way he's done it, I have a question out to how automatic the GPS connection/redirection is upon reconnection of the device (ie: do you need to reconnect it manually or is it automaic) and if it's not automatic right now, I'll stress that it needs to be.
It did immediately get coordinates when I connected it to my Holux 236, where the internal would take 10-15+ seconds and the coordinates would wander around for a while. This got coordinates and they stuck... I watched carefully and I saw the latitude go .605 to .606 then back to .605 a few times.. I didn't make sure they were accurate yet, I'll do that later, but by eyeball they were.
It doesn't seem to report sats fixed nor sat signal levels.. I'm concerned this might make some apps think there is no fix and wait forever for it. GeOrg and GPS Test seemed to not care, they reported the right location and it seemed to work.
I did not put it through any real life tests, just sat in my car in the parking lot at work and checked out my location.
I'm concerned if other important info like altitude, bearing, and speed are reported. I'll update when I get a response to the email of course.
One more thing I forgot to ask but I'll see in practice is if using this I can still use the electronic compass. Not that it's great, but it is convenient. Honestly though I'll still be happy without it.
There is a free trial that disconnects every 10m, or a 2 euro paid version. Very reasonable.
Author responded, he sounds right on top of the current limitations and is working on them. I suspect once he has worked on this a tad more, it'll work great. Give the trial version a try and see how it works!
I found that nearly all of my geocaching programs "just work", no fuss. I found that Google Earth gets an accurate fix but can't seem to find "My Location". Both seem to be because he's working on getting the satelite fix data into the program, if possible. Right now it reports 0.
Built-in compass still works fine!
He'll be working on automatic reconnection after he tweaks a few more things and sees what kind of efficiencies he can make and bugs he can drive out.
I was successfully using GPS Mouse with stock Eclair 2.1 & my GlobalSat Bluetooth GPS with my running program.
I have since flashed to Froyo JPO rom & now when I try & use the program I feel a vibration in the phone, the screen soon goes black & then does a mini re-boot & back to my home screen again??
I done some google searches but cannot seem to find an answer to thsi particualr issue
addo1962 said:
I was successfully using GPS Mouse with stock Eclair 2.1 & my GlobalSat Bluetooth GPS with my running program.
I have since flashed to Froyo JPO rom & now when I try & use the program I feel a vibration in the phone, the screen soon goes black & then does a mini re-boot & back to my home screen again??
I done some google searches but cannot seem to find an answer to thsi particualr issue
Click to expand...
Click to collapse
I'm using Bluetooth GPS Provider now, it works FLAWLESSLY, start and forget it while I'm using the GPS. Even if the GPS disconnects, phone is in standby extended periods, etc, always immediately reconnects and works.
As for your specific problem, dunno, but give it a try.
http://www.appbrain.com/app/bluetooth-gps-provider/de.mobilej.btgps
reboot bluetooth gps
addo1962 said:
I was successfully using GPS Mouse with stock Eclair 2.1 & my GlobalSat Bluetooth GPS with my running program.
I have since flashed to Froyo JPO rom & now when I try & use the program I feel a vibration in the phone, the screen soon goes black & then does a mini re-boot & back to my home screen again??
I done some google searches but cannot seem to find an answer to thsi particualr issue
Click to expand...
Click to collapse
I have the same problem, anyone a solution ? Please ....
Try Bluetooth GPS Provider, it works awesome for me. Reconnects immediately, works great.
If you have a ROM-specific issue, you need to talk to the ROM cook.
Samsung released an official update for JI6 via Kies Mini. This is ideal for those who aren't rooted or are experiencing issues with Odin.
http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=560&AT_ID=341559
Requirements: Windows XP, Vista, Win7 (all 32-bit)
Improvements:
Avatar: Added checking routine for file corruption
Swype: Applied updated build of Swype
Thinkfree Office: Applied updated build of ThinkFree Office
GMS: The Google Mobile Services has been updated
DLNA: Backbone updated
Kernel: 3D library patch
Telenav: APK updated
Kies: Can now be quit with Home key
Hard Reset:When performing a hardware key reset, data is erased
Modifications:
Radio: 3G antenna bar patch
SNS Sync: The interval value for synchronizing has been changed
Task Manager: String change to Internal Memory
Additions:
Media Hub: Samsung Media Hub is now available
Message Alert: Alert message added for Yahoo email over WiFi
Fixes:
Ringtone: Ringtone disappearing corrected
Silent Mode: No sounds play after unchecking silent mode
Feeds & Updates: Force close problem addressed
Calendar: Force close problem addressed
Contacts: Unknown name addressed
SNS: Contact sync error addressed
MMS: Out of memory exception addressed
This has been confirmed as the same as tmo ota via official samsung twitter
Sent from my SGH-T959 using XDA App
Can someone pull this update and pack with the kernel in an update.zip for us. Please please. I've been on vacation and won't see my laptop till friday. I'm itching for the update!! Thank you
Sent from my vibrant
allen099 said:
Ringtone: Ringtone disappearing corrected
Click to expand...
Click to collapse
Interesting, I thought it was OCLF or something doing that... it was just a stock firmware issue?
If we flashed JI6 through ODIN, can we re-flash it through KIES?
mrnosox said:
If we flashed JI6 through ODIN, can we re-flash it through KIES?
Click to expand...
Click to collapse
That's a negative ghost rider
Sent from my vibrant
mrnosox said:
If we flashed JI6 through ODIN, can we re-flash it through KIES?
Click to expand...
Click to collapse
You are already running JI6.
dasunsrule32 said:
You are already running JI6.
Click to expand...
Click to collapse
Yeah but there is some question as to whether or not it works right. I'd like to make sure it's the official one. Will it screw me up if I flash JFD through ODIN and then use Kies to update?
mrnosox said:
Yeah but there is some question as to whether or not it works right. I'd like to make sure it's the official one. Will it screw me up if I flash JFD through ODIN and then use Kies to update?
Click to expand...
Click to collapse
Yes that's how you would do it. But I dont think this version is any different then what your already running . Try it out and let us know.
Sent from my vibrant
can someone confirm that this update is the same from the other JI6 threads. once i updated my phone through odin i have missing applications in the market. though i don't really need the missing applications.
search for the application Desktop Visualizer on the other builds, then search for it on this one
iynfynity said:
can someone confirm that this update is the same from the other JI6 threads. once i updated my phone through odin i have missing applications in the market. though i don't really need the missing applications.
Click to expand...
Click to collapse
Yep, this looks the same to me as one of the other versions of claimed "stock JI6" that I falshed on my friend's phone via Odin. This one of course has all the apps and such, since it's just an update and not the entire OS. It only took about 3 minutes to flash this one via Kies.
Hey guys, Im a little disappointed here.
I got the JI6 Installed on my phone both from OTA, and KIES.
And ever since I bought my phone I have never gotten GPS to work correctly.
All these fixes, that we have gotten so far is enhance how your phone tracks you through wireless networks, and not one of these fixes has actually fixed the GPS it self.
Here is my dilemma, sometimes I am forced to use airplane mode, but am allowed to have GPS on, to use applications that only rely on GPS.
Well the minute I go into AIRPLANE mode with GPD on. All GPS functions go to hell since the phone can't use any wireless networks in airplane mode to track me. So I am forced to use my good ol G1 instead hehe.
My question is, has anyone else noticed having this problem? Because I am really starting to think that this is more of a hardware issue and not software. And all these new updates are made to use wireless networks more efficiantly in order to cover up the GPS fail.
I am inclined to agree with you. The Vibrant has to be the worst gps I have ever used. I will be sitting still and it has me jumping from street to street in my neighborhood jumping with Incredible Hulk like distance. It renders traking your phone through lookout useless.
I feel that smasung dropped the ball on the gps hardware and that is the root of all our issues. It seems the cut corners to save by using a bargin bin gps chip is bitting the in the ass. I also feel if the issue is in fact never rectified that it would be a great case for cals. It is sad when a phone that is this costly can not be used as a reliable gps solution.
I love this phone don't get me wrong but if I would have known of all the issues with gps and the faults of the rfs file system and lag attributed to it I would have probably went for another option. I really hope that sammy loses the RFS it is utter crap.
So, this didn't work for me. It tried to flash, said it couldn't, and now I've just got a screen with a picture of a phone, a computer, and a yellow triangle with an exclamation mark in it. Worse yet, it doesn't appear as if I can turn the phone off. Holding power makes the image go away for a bit, but then it always comes back. I have removed the battery, and when I put it back in, or plug in the USB, the image comes back. I'm going to try to use ODIN to recover, once that's done downloading.
s73v3r said:
So, this didn't work for me. It tried to flash, said it couldn't, and now I've just got a screen with a picture of a phone, a computer, and a yellow triangle with an exclamation mark in it. Worse yet, it doesn't appear as if I can turn the phone off. Holding power makes the image go away for a bit, but then it always comes back. I have removed the battery, and when I put it back in, or plug in the USB, the image comes back. I'm going to try to use ODIN to recover, once that's done downloading.
Click to expand...
Click to collapse
You're bricked but don't freak out. Unless you were using Voodoo, then you kinda need.to.freak out. If you weren't using Voodoo, then you should easily.be able to recover it using ODIN. I suggest using v 1.3 because its more stable. Grab the zip file in the ODIN stock JI6 tjread
I was able to fix it. Oddly enough, I couldn't really get ODIN 1.3 to work, however, ODIN 1.0 worked just fine to restore. Neither of them really let me flash the JI6 update, though. I ended up flashing Bionix 1.8.
bbuchacher said:
search for the application Desktop Visualizer on the other builds, then search for it on this one
Click to expand...
Click to collapse
Im using the.Kies update.and nothing shows up when i search for.that.
belial20xx said:
I am inclined to agree with you. The Vibrant has to be the worst gps I have ever used. I will be sitting still and it has me jumping from street to street in my neighborhood jumping with Incredible Hulk like distance. It renders traking your phone through lookout useless.
I feel that smasung dropped the ball on the gps hardware and that is the root of all our issues. It seems the cut corners to save by using a bargin bin gps chip is bitting the in the ass. I also feel if the issue is in fact never rectified that it would be a great case for cals. It is sad when a phone that is this costly can not be used as a reliable gps solution.
Click to expand...
Click to collapse
I'm inclined to say that it's poor quality control, not necessarily hardware. My 1st vibrant had satisfactory GPS with JFD, but had to be returned due to build quality issues. My new vibrant has rock solid build quality, but a horrible GPS. Even updated to JI6, it's completely unusable. Some phones work well, others are inoperable.
ran kies mini and installed update with no issues. didn't lose any data, but you lose root access (until you root again). my V was rooted with JI2 gps fix and adw launcher. my gps gave me ~25ft accuracy after JI2 and its the same after JI6 update.
after applying the attached zip through CWM the GPS is finally working!
instructions:
1. apply the fix through CWM
2. in LBSTestMode:
a. verify all values in the application test are default
b. in the SUPL put supl.google.com and change the port to 7276 with no secure socket
c. wipe GPS data
3. after the first fix (~3 minutes) you will get a fix instantly almost in any condition at any time
the fix was validated on 2 different vibrants with GPS issues
goodluck
big credit to:
Mr. Pilot
BobLeponge23 & johndoe1000
No offense, but who are you? I'm not one to flash random zips I download off the internet.
stealthx32 said:
No offense, but who are you? I'm not one to flash random zips I download off the internet.
Click to expand...
Click to collapse
He got this from the i9000 forums. I've personally used this, and it helps with the gps dramatically.
Sent from my SGH-T959 using XDA App
This is an old, well known pre-JI6 fix. DO NOT APPLY! This also NOT development related, try the General forum next time.
Hi all,
you can say what you want about this fix however, both I and BobLeponge23 have vibrant's phones with GPS issues.
we have tried all possible fixes:
JI6, JI2, JK2, JK6, samsung restore app, changing all the settings through LBSTestMode
nothing worked until we tried this fix.
The change is instant.
we have now a working GPS under:
the new axura 2.1 (JK6) and Obsidian_V5_beta (with modem JI6 installed).
Ok. Won't argue with that. Whatever works for ya!
Do you have "Use wireless network" unchecked? And WiFi off? With only "Use GPS Sat" checked? Cause that is the only way to see if your GPS is really fixed.
Sent from my Samsung Vibrant Galaxy S using XDA App
in LBS Test mode you wont get fix just with wireless networkor or WiFi.
in general when the GPS icon is flushing you dont have a satt. fix although
you might get general fix from the wireless network.
DreamcastDC said:
Do you have "Use wireless network" unchecked? And WiFi off? With only "Use GPS Sat" checked? Cause that is the only way to see if your GPS is really fixed.
Sent from my Samsung Vibrant Galaxy S using XDA App
Click to expand...
Click to collapse
That's not a good test for phone GPS units. The phone's GPS uses network location to help get a faster fix. Apps like GPSTest, GPSStatus, and LBSTestMode won't report a GPS fix with only a network/wifi fix, so I don't understand the obsession with this sort of a test. All it will do is slow down your GPS locks.
Disabling wifi does make a difference on newer firmware (worked on JFD, but JI6 and up broke it). With wifi connected, the phone doesn't download the GPS data properly, so it acts like a standalone GPS and will take a long time to get the needed data from the GPS sats.
The GPS chips in our phones are NOT designed to get fast locks without assist data. Even the ones that are, sometimes take a while for the accuracy to really get good because of this data. That's why you should have a data plan for best results. The GPS needs data to calculate your position. It can get the data from the sat network, but that's SLOW. Getting it over the internet is many times faster, even over GPRS. That's one reason why it's irritating that wifi doesn't work with it. Those without data plans are basically screwed. GPSStatus seems to be able to get it over wifi, so you can try that. The data should be good for up to 24 hours.
I have no idea what this fix does, and I won't be installing it as I'm satisfied with the GPS performance post JI6 with my phone. Even with JFD, it worked fine once I set the supl settings up.
they are sharing a fix.
[highlight]Mod Edit: Watch your language[/highlight]
epakrat75 said:
This is an old, well known pre-JI6 fix. DO NOT APPLY! This also NOT development related, try the General forum next time.
Click to expand...
Click to collapse
Honestly, it worked for me on JK6.....
Sent from my SGH-T959 using XDA App
If this is working for folks where flashing Axura 2.1 didn't then, that's all that matters. Go for it. However as I'm running Axura 2.1, I have no need of this.
I just don't want people thinking this is the ultimate fix and breaking their phones trying it. I've seen it happen with simpler fixes.
I was using a jk2 rom also, and GPS would work at times, even in a large Metro area. i flashed this, and now I even get GPS locks inside of buildings where it would never lock before. I am happy. Indoors, it gets a lock in about 10 - 12 seconds, outdoors about 5 or less.
I don't understand how it can work, it uses jupiter.xml subsystem that TMO US Vibrant lacks
lqaddict said:
I don't understand how it can work, it uses jupiter.xml subsystem that TMO US Vibrant lacks
Click to expand...
Click to collapse
JK2 and JK6 now use the Jupiter xml
is this working in eugenes ginger clone?
is this working in eugenes ginger clone?
It worked for me! Why don't you just test the files and see why it works instead of whining?
saved
10char
well fellas, i have so much dragons in the vibrant already i figure what could possably go wrong now lol. Running nero beta 3 and it actually works,got an instant lock on precisely where i was,dident had that before with all the other fixes,couldent believe it but yep works. Thanks for this fix
Didn't make a difference for me. Since JK2 ive always got a fix in under a minute. With this installed it was over a minute but under two minutes. I'll keep it for a day to side if anything changes and report back.
I'm running a vanilla SxE4.1 with super io kernel.
Sent from my SGH-T959 using XDA App
Hey Everyone
I recently installed XXJVB (2.3.3) onto my sgs and it works really well. my only issue is that the wifi connects sometimes and sometimes it doesn't. This happens at home often and is really annoying.
Does anyone else have this problem?
And does anyone know how to fix it?
Thank you for any reply's
I haven't experienced it.
First thing to try before you go any further.
Turn off everything that connects to your Wi-Fi router. Unplug the router from the power supply for a minute, then plug it back in. When it boots back up, see if the problem still persists.
Also, Have you tried a factory reset prior to or after flash?
had that issue when I played around and installed a cpu tool from the market: my wifi acted up same as yours. As far as I could deduce it was because the power/sleep settings were altered -- beyond my pay scale. Uninstalled the offending program and rebooted: the whole system was hickey and media scanning was an issue. So, did a recovery restore in cwm and all is well again.
Suspect the issue is the set up for power management. sleep policy and the other internal setting sin the kernal being out of phase with each other. Do a retore to the last stable system you had.
I have also leanred the value in doing a complete backup before I play with any new themes and mods: that way restore bails you out!
Did you notice that on version 2.3.3 wifi sensitivity worse that on previous version?
Using "Wifi analyzer" application I found that on Gingerbread kernel signal weaker then on 2.2.1 by about 10 db.
I've tried to use modem JPY (from 2.2.1) instead of native JVK but it didn't help.
It looks like somewhere there are wifi parameters that should be configured properly.
SOLVED
Thank you everyone for you input
@electrotune1200
Thanks for your idea's. The whole turning router off and on worked. i feel rather stupid cause i have to do that often so that i can get my laptop to connect, never even crossed my mind to try it for my phone lol.
Thanks again everyone