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
I have been doing enough hacking of my Captivate, I got 2.2, rooted it, installed tons of stuff (most of witch I am sure I do not need)
but anyways, any quick hack to get HSPA on my Captivate, with a update.zip or something. also, I read that sometimes BlueTooth stops working right, I use it a lot so thats not an option
Ideas?
thanks
captivate roms dont show an "H" but hsdpa is enabled. hsupa on the other hand need an i-9000 or vibrant modem.bin and for some inexplicable reason breaks bluetooth audio but not bluetooth connectivity. bluetooth file transfers work and pairing works on all devices but the audio comes through messed up. if you dont like it get a sim unlocked vibrant or an i9000. the devs are still looking for a solution as far as i know but i may not be up to speed in that area. now there are many modem.bin files and kernels for the i9000 and vibrant have been modded to work on the captivate in both eclair and froyo so there may be a working combo that i just dont know about.
eatonjb said:
I have been doing enough hacking of my Captivate, I got 2.2, rooted it, installed tons of stuff (most of witch I am sure I do not need)
but anyways, any quick hack to get HSPA on my Captivate, with a update.zip or something. also, I read that sometimes BlueTooth stops working right, I use it a lot so thats not an option
Ideas?
thanks
Click to expand...
Click to collapse
congratulations, you have just asked what everyone has been asking for months now.....
as of right now, if you want HSUPA (we already have HSDPA), you will lose some Bluetooth capabilities....its a fact and there are lots of devs working on making it work right....unless you can code, i would suggest you just read the dev forums and wait for a proper kernel/rom combo to become available for you to use.
Hey all,
So basically I just bought my first android phone couple of weeks ago. Its the Samsung Galaxy S GT-I9000 running 2.33 Firmware.
It is not yet rooted (have read some articles found in these forum found them really helpful)
but I'm not gonna root it for now I think cause this is my first android phone Im still a noob (used to apple)
Now my problem is I will be going abroad in 2 weeks and could really use the GPS.Tried donwloading GPS Status but i never actually got a lock on the satelites (or it took too long that I gave up) I also tried the fix but the code (but when dialing *#*#1472365#*#* nothing happened lol)
I also downloaded loads of GPS software such as AndNav2,Wisepilot,Navigon,CoPilot,Sycig but 90% of those gave me an error when I try them such as this software cannot be started on your device.
Is there any good GPS software/app which does not require an internet connection (pls not offline maps but like turn by turn app or similar.)
Thanks a lot.
Personally i use Copilot live 8
maybe you could flash the phone to a clean stock ROM and then try again ??
Good Luck!!
So I finally managed to fix it and get a fix on the satellites
Now my last problem is, I need a good turn by turn app that does not use internet (except maybe for downloading maps first time etc.)
Thanks.
Hmm anyone?
I'm using Navigon. You need an internet connection to download the maps. Following that, there is an option to turn off internet connection. Go to Menu>Settings - second option from the top.
in my personal experience... you need to learn how to root, flash firmware, etc...
i'm also a noob and used to apple devices..
before my galaxy s get great firmware (thx xda-dev), i miss my iphone so much...
but after flashed with great firmware, everything working great, nice apps.. and so on,
also a great benefit for me, i know how to do those things... and i can say bye2 for my apple devices now.. even one great iphone 5 wont help me back to apple
just PM me if you need anyhelp
hope you enjoy your sgs as much as i do...
shinkid said:
in my personal experience... you need to learn how to root, flash firmware, etc...
i'm also a noob and used to apple devices..
before my galaxy s get great firmware (thx xda-dev), i miss my iphone so much...
but after flashed with great firmware, everything working great, nice apps.. and so on,
also a great benefit for me, i know how to do those things... and i can say bye2 for my apple devices now.. even one great iphone 5 wont help me back to apple
just PM me if you need anyhelp
hope you enjoy your sgs as much as i do...
Click to expand...
Click to collapse
Actually Im used to apple too and my phone was jailbroken too so I will root this one soon probably too. but yeah I could use some help
So I downloaded Navigon and connected to my pc, installed maps used for couple of sec it was great app I have to say but then I started to crash on me every time ;(((
RiKKu28 said:
So I downloaded Navigon and connected to my pc, installed maps used for couple of sec it was great app I have to say but then I started to crash on me every time ;(((
Click to expand...
Click to collapse
exact error here:
The application Navigon (process.com.navigon.navigtor_checkout_eu40) has stopped unexpectedly. Please try again later.
All I can do is choose force close.
Hello All,
Have just started using this forum and failed to introduce myself previously, my name is Jay; I am 27 from DC but in Afghanistan for a few more months (yea..sucks) new to rooting, flashing and all that but I have recent interest in it and it passes the time better than most thing we are "allowed" to do over here.
I just switched from a HTC Desire to a Galaxy Captivate
So far...I have unlocked it (via cellunlocker.net), upgraded to the leaked 2.3.4 Gingerbread, Rooted using the 10step method posted here, Installed Victory v1.5 Rom, tried flashing Talon kernel but bricked the phone and had to redo the above...
My question is to those more knowledgeable than myself with all this...what is the best Kernel, Rom, Modem...whatever else...that I can have on this device to keep it running smoothly, fast and reliable?
I do all the basic call, txt, surf...play games, watch movies, use apps, etc...not a developer but want my phone to be tweaked as much as possible so it does not seem outdated or lag with new things being added.
My current settings are:
Baseband I897UCKH3
Firmware 2.3.4
Kernel 2.6.35.7-I897UCKH3-CL461307
Build VictoryRom_v1.5
There is nothing wrong with the phone...as I said above, if I could do more to it and have an overall better device and pass some time here I would enjoy that. Victory seems great but all I notice myself is the battery indicator has changed and...thats about it (a lot likely goes unnoticed by me)
I do have one problem with the phone that maybe a different modem can fix? (I hope) for some reason my GPRS will not work out here with my browser...I can use the market and apps that connect to the internet but my browser seems to be WiFi only. I have changed the settings from usa to europe since I am using a sim from over here but no luck...and added the gprs settings to the phone which allowed apps internet access but zero for browser..any ideas?
I really thank anyone who takes the time to reply...I am sure teaching a new person in this is annoying just as showing the new guy here how to clean his weapon...lol...but we were all new at everything once and I thank you all for reading my novel
-Jay
Jay,
Thank you so much for your service and contribution to our freedom, I know it must be hard to be away from the life you once knew. Hang in there It's not for nothing. Hopefully someone will be able to help with your GPRS settings. I am running the same setup on my captivate only I have used Boogs kernel to install clockwork recovery as well. You can flash boogs kernel over the kernel you have now and that will let you flash roms or speedmods later. If I were you I'd keep my eyes peeled for GPRS settings in your area and wait for EXT or speedmod kernel for the 2.3.4 They are saying RFS is pretty quick to begin with though. It may be hard to beat but im sure one of these great Devs will figure out a way to make 2.3.4 smokin fast. Once again thanks for doing what you do. Keep your head down Soldier!
Steve
If you like using your mobile providers Net, you might give I9000 ports a try. They allow for better Upload speeds but you will sacrifice Audience chip support (noise suppression processor that only I897 have). Also since I9000 source usually drop first they have all sorts of kernel mods like Voodoo sound, Voodoo color fix, BLN, init.d files tweaks like V6, among many more. Sadly I897 native roms always play catch up with I9000's.
Personally I prefer native rom, because they tend to run smoother for longer periods of time (I9000 tend to slow down over time on my phone, but thats just my experience) and I don't use ATT's network a whole lot (90% of the time I'm around a wifi connection) and I like the audience chip, it is a phone before anything else.
Edit: Also there isn't a "best" rom, kernel or modem. Each rom has their own pros and cons, same as Kernels. And no 2 phones are the exact same so not all of them take well to all the tweaks, mods, etc. And most of the time i9000 kernels wont work with i897 roms, at least in GB.