Database Develop

[SOLVED] Is Bluetooth broken in JM5/JM7 ?

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

[Q] bell galaxy s UGJG9 vs. UGJH2 differences

Hey guys, my samsung galaxy s has the UGJG9 firmware installed. was just wondering what the difference is between that and the latest one?

New JH2 + SPL fix
Samsung Mobile Canada Thank you for your continued patience on the three-button reset issue. Your feedback is important to us and we are pleased to provide a resolution for Bell Mobility’s GT-I9000. Please find full details posted in the link below.
Samsung Galaxy S Vibrant (GT-I9000) Software Upgrades for Handsets with Original Production Software
A software upgrade is now available for Bell Mobility Galaxy S Vibrant handsets, provided the device has original production software (JG9). The latest version of Kies has been tested and will resolve the three-button recovery issue. Please note, this solution is for Canadian devices only....
By:Samsung Mobile Canada
Click to expand...
Click to collapse
http://www.facebook.com/samsungmobilecanada
Apparently they released the JH2 again but including a SPL fix, so people already on JH2 will need to flash back to JG8 or something, then flash forward to JH2 again to get the new SPL fix

I got JH2 the other day. Yesterday my phone was going retarded, freezing and losing signal when it never had before. Seemed ok last night and today though I haven't spent much time with it today.
GPS was totally out of whack last night, sitting still and my location was jumping all over the place. Google navigation is unusable. Checked compass in GPS essentials and it was fine but in nav it just spins around and can't get it right.
Youtube widget changed. Now shows most viewed on the main bar but video and search buttons are not functioning properly. Right now it only shows the search button. If I search or launch youtube then go back the video button will be there but neither thet nor the search button will work. Wish I had just left it alone.

did you get the update with the spl fix?
and was your 3 button mode working for you before?
if not does it work with the new update?
lol so many questions... and thanks for the replies and the update on the firmware.

Just update dude. Everyone is experiencing various issues regardless of the firmware. I run 3 to 4 times a week using endomondo and the GPS tracks my route almost flawlessly. A few hitches here and there but nothing horrible.
My 3 button combo wasn't working at all and I was already on JH2. Had to do the registry trick to get Kies to flash the new JH2 on my phone and now it works. Upgrading to the new JH2 is the best choice to make, especially if you have plans on using a few mods.
I highly recommend the battery mod available on this forum after you upgrade. The SGS stock battery indicator is horrible and inaccurate, and I rather not waste my homescreen space on a battery widget.

Ya, did the update a few days ago. Three buttons work now and my gps doesnt think im in japan anymore (ya it was that bad) anyway definitely worth the update.
Sent from my GT-I9000M using XDA App

My 3 button mode worked before the update, I haven't tried it since. I haven't rooted and not sure yet if I will, will see how official 2.2 goes first.
Still losing signal though. Yesterday the girlfriend tried to call me and said she either got a busy signal (WTF) or it just went straight to voicemail.
Today I tried to make a call and had to redial two or three times because it kept losing signal. Def a problem with the phone and not anything to do with reception in my area. Only phone calls though, never lose signal when using data or market ect.

Guys, I'm a bit dense on this subject so please be kind.
I have JH2 on my Galaxy. I can't remember if I updated to this version via Kies.
So far, the 3-button recovery problem has not affected me. I haven't rooted Android (since I don't need SU rights), I haven't yet unlocked the phone (no need) and I haven't attempted any Android system updates. I guess I could be called an average user. I haven't tested the 3-button issue.
What circumstances could arise down the road, which would make it necessary for me to do a 3-button recovery? In other words, is this a problem which could affect all Galaxy owners?
Thanks.

androiderer said:
Hey guys, my samsung galaxy s has the UGJG9 firmware installed. was just wondering what the difference is between that and the latest one?
Click to expand...
Click to collapse
I updated to JH2 prior to the SPL fix inclusion and found it to be better than JG9...smoother and less lag issues. Just make sure to backup everything.

My phone is still on jg9. It never had the three button issue it always worked for me. If I upgrade to jh2 how will this affect me?
Sent from my GT-I9000M using XDA App

MaestroSeven said:
My phone is still on jg9. It never had the three button issue it always worked for me. If I upgrade to jh2 how will this affect me?
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
if it was working, it will continue to work
if it was NOT working, it will now work

TheChancellor said:
Just update dude. Everyone is experiencing various issues regardless of the firmware. I run 3 to 4 times a week using endomondo and the GPS tracks my route almost flawlessly. A few hitches here and there but nothing horrible.
My 3 button combo wasn't working at all and I was already on JH2. Had to do the registry trick to get Kies to flash the new JH2 on my phone and now it works. Upgrading to the new JH2 is the best choice to make, especially if you have plans on using a few mods.
I highly recommend the battery mod available on this forum after you upgrade. The SGS stock battery indicator is horrible and inaccurate, and I rather not waste my homescreen space on a battery widget.
Click to expand...
Click to collapse
how do you do this hack, i wanna put my bell rom back on the phone, i flashed to 2.2 froyo and wanna go back to bell rom now.
please link me

hansonator said:
My 3 button mode worked before the update, I haven't tried it since. I haven't rooted and not sure yet if I will, will see how official 2.2 goes first.
Still losing signal though. Yesterday the girlfriend tried to call me and said she either got a busy signal (WTF) or it just went straight to voicemail.
Today I tried to make a call and had to redial two or three times because it kept losing signal. Def a problem with the phone and not anything to do with reception in my area. Only phone calls though, never lose signal when using data or market ect.
Click to expand...
Click to collapse
I havent been able to update to JH2 from JG9 (trying to use kies but thats a prize in itself) but I have in the past gotten where I would try to call, and as the call dropped while still dialing it would tell me the radio is off. Or it would tell me im in airplane mode etc.
Now for the last 24 hrs I have yet to be able to make a call, although datta and texting works perfectly fine, every time I make a call it says my radio is off. And the same problem when someone calls, they are lucky if they get a fast busy signal.
Im talking with bell to get a replacement in store, if not I have a 'insurance' plan that'll give me a loaner etc while they ship it out.
Any update on whether your phone is still dropping into Flight mode?

[Q] Froyo GPS Lock Problem

Ok...so after updating to Froyo my GPS is not working. Not only that, my phone can't seem to find my approximate location even after enabling "Use Wireless networks". I used GPS Status app from the market and I confirmed the phone was seeing several satellites, but it was getting no lock. I had no problem with my GPS with 2.1 aside from losing my location occasionally when I drive through the downtown.
Is anyone else experiencing this issue? I'm running my phone on Rogers network, unlocked and rooted.

Yeria said:
Ok...so after updating to Froyo my GPS is not working. Not only that, my phone can't seem to find my approximate location even after enabling "Use Wireless networks". I used GPS Status app from the market and I confirmed the phone was seeing several satellites, but it was getting no lock. I had no problem with my GPS with 2.1 aside from losing my location occasionally when I drive through the downtown.
Is anyone else experiencing this issue? I'm running my phone on Rogers network, unlocked and rooted.
Click to expand...
Click to collapse
You didn't say what version of Froyo you are running but I'd change my modem file and use one of the alternate ones that DocRambone has. There's a thread on this but I find the ZSJPE (Hong Kong) version to be superb (and our company develops an app for the phone that uses GPS for golfers) - very quick, very accurate...

Oh I'm using JK4 from Bell..and kernel version 2.6.32.9....
Edit: Oh and I have also done factory reset/cache wipe...and it's still doing that...I want to see if I can fix this without changing the modem file or anything like that...

I'm having the exact same problem since upgrading to the official 2.2 release from 2.1
EDIT: Bell Galaxy S Vibrant, Unlocked and running on Rogers. Not rooted.

sw411 said:
I'm having the exact same problem since upgrading to the official 2.2 release from 2.1
EDIT: Bell Galaxy S Vibrant, Unlocked and running on Rogers. Not rooted.
Click to expand...
Click to collapse
Ok...so I'm a bit relieved to know I'm not the only one out there...From the things I've been reading it doesn't seem to affect phones running on Bell networks..but shouldn't GPS be not affected regardless of the network you're running on? I don't see why it's refusing to get a lock...

I can't believe no one else is having this problem, maybe we're the only ones unlocking??

I was also having this problem. I updated to bell froyo using kies, and am unlocked using rogers. I loaded gps test, set it so it wouldn't shut off the screen, and let it run for about 30 min in a window. Eventually it got solid lock on a couple sats and it now seems a lot snappier to get a lock.

sw411 said:
I can't believe no one else is having this problem, maybe we're the only ones unlocking??
Click to expand...
Click to collapse
Ok, good news! At least for me anyway... I decided to try keeping my GPS on and let my phone to try and find my location..however long it was going to take. I don't think it took me 30 minutes but it took me good 10 minutes before my GPS found my location. I think the problem was because I'm having trouble getting location information based on my wireless network and updating to Froyo and doing a factory reset must have deleted my satellite schedule. Right now I'm just so glad to find out my GPS isn't broken! :-D You should try the same thing I did.
Sent from my GT-I9000M using XDA App

@sw411 Oh and you should try and read this forum about wireless network based location service.
http://forum.xda-developers.com/showthread.php?t=845152
Sent from my GT-I9000M using XDA App

Thanks Yeria, that sounds like the problem we're having.
I do find that if I give it enough time, It will get a pure GPS lock, but I'm not getting any aGPS (the network based)
That thread you link sounds like the solution, but unfortunately I can't seem to access the file they tell you to modify

I too have GPS problems right after upgrading to official froyo. And it kept getting worse when i tried custom ROM. I tried factory resetting and format all my sd card, cache wipe etc hoping that it will return to normal like when i was in 2.1 elcair but to no avail. I don't know if some bad code was left behind when i did the official upgrade through kies. All i can say is it was working fine when i was at 2.1 then suddenly went bad after 2.2.
By the way, my problem is my GPS lock kept of disconnecting every now and then thus rendering my GPS useless as it kept on displaying my location as "off road" even though i'm on a clear highway with clear and bright skies!

ahh, if I root the phone I can get to
/dbdata/databases/com.google.android.gsf/gservices.db
unfortunately, this phone doesn't have sqlite3 installed!! I need to try and find that
EDIT: Found a copy of sqlite3 and was able to push it to the phone. edited the db as people suggested! I'll have to test it on Monday

mikextr23 said:
I too have GPS problems right after upgrading to official froyo. And it kept getting worse when i tried custom ROM. I tried factory resetting and format all my sd card, cache wipe etc hoping that it will return to normal like when i was in 2.1 elcair but to no avail. I don't know if some bad code was left behind when i did the official upgrade through kies. All i can say is it was working fine when i was at 2.1 then suddenly went bad after 2.2.
By the way, my problem is my GPS lock kept of disconnecting every now and then thus rendering my GPS useless as it kept on displaying my location as "off road" even though i'm on a clear highway with clear and bright skies!
Click to expand...
Click to collapse
Based on what I have found so far, and assuming your aGPS or any other wireless based assistance features are not functioning properly, doing a reset and cache clear will not help with your GPS at all. I have read that the phone will try to download the satellite schedules directly from GPS satellites if you're using purely satellite based GPS option. It'll be slow so it will take longer to get a lock and that's why phone will use other means to shorten the lock time. Once the schedule is downloaded, they said there shouldn't be any problem until the schedule expires, at which point you will have to download the schedule again.
I think the reason you're losing lock frequently might be because your phone doesn't have a clear view of the sky..? I used my phone GPS to drive around Toronto, Vaughan and Mississauga last night for at least 4+ hours, and I did not have any problem.

So, I tested today after updating the db.... no agps still..
Anyone else still.having issues with agps?
GPS works, just no agps since 2.2
Sent from my GT-I9000M using XDA App

mikextr23 said:
By the way, my problem is my GPS lock kept of disconnecting every now and then thus rendering my GPS useless as it kept on displaying my location as "off road" even though i'm on a clear highway with clear and bright skies!
Click to expand...
Click to collapse
This is why I unfortunately have to use an old Tom Tom GPS!

i'm having this problem too. i finally got it picking up quickly on 2.1 but once i updated i haven't been able to ever get a solid lock. has anyone found a solution yet??

Now that my wireless location service is kind of working I thought aGPS should also naturally work but I guess not... My GPS takes a pretty long time to start up and I haven't found any fix for this..
It's funny because I didn't really have any problem with my GPS with 2.1 but now I do with 2.2...
Sent from my GT-I9000M using XDA App

SGS/Doc's Rom Questions

Just cooked and installed a rom on my Telstra GT-I9000T handset and I couldn't be happier. The speed has more than doubled and I am free from Telstra refusing to release updates and their bloatware. Any way I have some Questions.
I'v installed Doc's 9.6.6 Rom and it's going quite well.
1. The GPS has improved but I think it could still be better. I see there is an APP out there called GPS Aids and I was wondering if it would improve my GPS functionality or would it not work with a custom rom like mine?
Are there any methods to make my GPS better? I feel that this is the phone's achilles heal.
2. I now have the option under settings > About Phone > Software Update. I guess Samsung or Google will make Gingerbread avaliable for the SGS soon. When it is will i be upgraded OTA with this software update feature?
3. Any word on when gingerbread is coming out and if/when it will be avaliable in the RomKitchen? I know it's in Beta testing at the moment. Can't be too long before it starts to get released around the globe.

1. You could try a newer rom/modem as they definitely help out with GPS. Currently on JQ1 I get a lock within 5 secs accurate to about 10m. You could also try Faster Fix from the market
2. Upgrade will happen when Samsung releases it.
3. Supposed to be coming out March but no one really knows.

gbatman said:
Just cooked and installed a rom on my Telstra GT-I9000T handset and I couldn't be happier. The speed has more than doubled and I am free from Telstra refusing to release updates and their bloatware. Any way I have some Questions.
I'v installed Doc's 9.6.6 Rom and it's going quite well.
1. The GPS has improved but I think it could still be better. I see there is an APP out there called GPS Aids and I was wondering if it would improve my GPS functionality or would it not work with a custom rom like mine?
Are there any methods to make my GPS better? I feel that this is the phone's achilles heal.
Click to expand...
Click to collapse
GPS Aids do works on Doc's ROM. What it does is speed up satellite discovery. So in theory you'll see satellites faster, but this doesn't necessarily means that it will be locked faster.
On my SGS it takes an average of 20s to lock using LBSTestMode. Some navigation apps takes longer though (not sure why). Also as utsmaster18 said, fasterfix helps too.
Latest DOC's ROM is 9.9.5 (based on JS8) and I've read (can't remember what thread) that ZSJPG modem is very good. I'm using JS8 + JPY CSC + ZSJPG modem, with Damian Kernel. I have gps aids and faster fix and I do love the GPS performance.
2. I now have the option under settings > About Phone > Software Update. I guess Samsung or Google will make Gingerbread avaliable for the SGS soon. When it is will i be upgraded OTA with this software update feature?
Click to expand...
Click to collapse
I don't think this function works at all. Even on my stock ROM this was useless. At least for me. I'd say you'll be best served by the XDA comunity.
3. Any word on when gingerbread is coming out and if/when it will be avaliable in the RomKitchen? I know it's in Beta testing at the moment. Can't be too long before it starts to get released around the globe.
Click to expand...
Click to collapse
Rumor says it would be out this month. In fact there is a leaked beta ROM already out and many custom ROMS built on top of it. But an official *golden* ROM from Samsung, I think that even they (samsung developers) can't tell for sure.

This is my ROM:
XWJS5_Wipe-v9_6_6-23-29-22-04-03-rM9FJUquQU
I got the GPS working.
First I used an ap called GPS Status to reset my GPS data as Dialing *#*#1472365#*#* does not work for me.
After I cleared all my GPS data I used FasterFix to add the fix although I am not sure if FasterFix was necessary as maybe clearing the data was all I needed to do.
GPS is really good now though.
I also got the compas working in GPS Status. First time I have had a compas work on my phone.

tfvaldo said:
I don't think this function works at all. Even on my stock ROM this was useless. At least for me. I'd say you'll be best served by the XDA comunity.
Click to expand...
Click to collapse
I have a mate with an old Nexus phone and he recieves firmware updates OTA. I never had this with my stock firmware (2.1-Update1) but Telstra probably removed it.
It will be interesting to see if I am able to update this way.

I may be wrong, but I guess Nexus firmware comes from Google itself, while we have to wait for samsung to release it. That's why we probably won't get updates through that menu.
At least on stock froyo (JPY) that menu hasn't worked for me. Not even to tell that I was running the most updated firmware. All I got was errors connecting to the server, or some other words with the same meaning

I'm pretty sure you're right and nexus firmware comes straight from Google.

GPS Aids and Doc's Rom works well together and gave me GPS lock in 2 minutes or so.
That's with JPE modem.
Now using Darky's 9.4, JQ1 modem without GPS Aids and getting locked in under 30 seconds with Google Maps and Navigation.
But I'm not knocking ROM creators around here, GPS Aids and Doc Rom FTW!
And yes, Nexus handsets get OTA directly from Google, no mobile operators in the damn way.

I might try GPS AIDS.
The clearing the data method with GPS Status then using Fast fix has made my GPS super accurate but it takes forever to get a fix and actually start working.

Just another question. Not really related to the OP but my provider has released 2.2 and there is a new modem JP9. Is it worth flashing this to my phone. I am running JL2 and it seems fine. Has any one compared JL2 to JP9?

Help with sister's i9000

Hey guys, I don't have an i9000, my sister does. I'm here visiting for the weekend and would like to help her clear up as many issues as possible. Unfortunately time is of an issue, I'm wondering if I can just name the problems, and could anyone please link to solutions/explanations? Many thanks if so.
Here are the issues:
-laggy homescreen (stutters between swiping screens. I've heard there is an app that be installed that fixes this?)
-cannot connect to android market (on 3G, no wifi in the house. Error msg says "cannot establish a reliable data connection to the server. This should be a temporary problem, or your phone may not be provisioned for data services. If it continues call customer care")
-battery dies in 4-5 hours (maybe a faulty battery, but maybe a software issue?)
-device (and screen) gets hot after some use (could be normal, I have a wp7 that gets hot on the back)
Her version of Android is: 2.1 (although it says "2.1-update1", but does nothing when you try and press it)
She is on Bell in southern Ontario, and is on a standard data plan.
Again, any help would be so much appreciated. Thanks very much in advance.

Laggy screens are common on 2.1, there are lag fixes and kernel mods that fix this issue, I can't really give you much more info then that otherwise I'd then be talking out my ass since I'm no expert. You can look about here for more info http://forum.xda-developers.com/showthread.php?t=966646
Another way to reduce the lag is by flashing a new ROM custom or stock, I'm on a stock 2.3.3 ROM and there is virtually no lag, which also can help with the poor battery performance. Check out here for stock ROMs http://forum.xda-developers.com/showthread.php?t=810682 and here for custom ROMs http://forum.xda-developers.com/showthread.php?t=886000
Sorry no idea about the Market problems though, you could try the online market and see if you can push an app to your phone maybe? https://market.android.com/?pli=1, or just look about more on here or the Goog machine
Battery issues, start with all the basics turning stuff off, haptic feedback, GPS, Bluetooth, Wifi etc... only enable apps/services when you need them, also as I mentioned a new ROM could also help with poor battery performance.
The 2.1-update1 is a version, you cant update it by pressing the button (when I was new to Android I did the same ) to update follow the instructions in the threads I posted.
Best thing to do is carefully read over everything before you do anything though, you don't wanna end up with a soft brick specially if download and recovery arent working *had to learn that one the hard way*

2.1.1 is a primitive version.....move onto 2.3.3 GB.....regarding Market....go to Settings>Applicatinos>Select market in the list>clear data. Ensure that this phone actually is subscribed to a dataconnection plan with the service provider

Install kies on a computer and see if there is any firmware update available. You will need a certain combination of files if you want to update to gingerbread using odin as your sgs is an american firmware.
Sent from my GT-I9000 using XDA App

Personally i would update through Kies to latest official firmware . Wait until Gingerbread 2.3 is released before going down that road ..
If you get involved in flashing someone else's phone its either going to work or you brick the phone especially for a newbie and in a short timescale .
jje

If you decide to update via Kies, it sounds like a factory reset is in the need either before or after the flash. Preferably a reset before upgrade, and a reset after. Should clean things up a bit.

JJEgan said:
Personally i would update through Kies to latest official firmware . Wait until Gingerbread 2.3 is released before going down that road ..
If you get involved in flashing someone else's phone its either going to work or you brick the phone especially for a newbie and in a short timescale .
jje
Click to expand...
Click to collapse
+1
Sent from my GT-I9000 using XDA App

Thanks very much guys. I've never flashed a rom before, but I'll look into it to possibly do it next time.
In the meantime I've advised her to call bell about the market problem and battery.
Thanks again.