Did anybody notice any interference when using a bluetooth headset whilst also having WiFi active on the i8700, particularly in range of a WiFi AP?
Yes, this has been a problem since the begining. I'm hoping new ROM will fix this, but this is rather annoying problem for Omnia 7
Ok after extensive testing of the Sound Tunner (*#0002#28346#), I will warn people that they SHOULD NOT mess with it to begin with. Changing those value will cause major problems that are irreversible (even if you change back to default values).
One of the problem is plugging your phone back to Zune, or the USB cable to charge, or the headphones will reset the volume level of the loud speaker.
I have reflashed my Omina back to XXJK1 and the problems are no longer there. So, once again, if people are thinking about messing around with this sound tuner. DON'T! Try the Media Volume Setting apps if you're still on 7004/7008. Other than that we can cross our finer and wait for future ROM release that potential solve these issue.NoDo did not resolve this issues, so I don't think we can rely on MS's part to fix it.
And what exactly does the sound tuner have to do with this problem?
On an additional note, the new KC1 firmware DOES NOT fix the problem.
Samsung is so good but so bad at making phones.....
This problem drives me crazy, I have BT speakers at home and a BT head unit in my car, the connection of the BT overall is poor, but music playback is unbearably choppy if you leave wifi on. My Samsung Focus does the same thing. The HTC Surround does not have this problem.
I honestly don't think this will ever get fixed, its just one of those software/hardware/driver issues that Samsung will NEVER fix.
I am crossing my fingers that the official mango release with whatever drivers is has fixes it, but I know that's probably not going to happen.
WiFi interference - one Omnia7 with & one without
I have two Samsung Omnia 7 phones. One unit has virtually unusable BT with WiFi turned on-
OS Version: 7.10.7720.68
Firmware revision number: 2424.11.9.3
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.9.1
Radio hardware version: 0.0.0.800
Bootloader version: 5.9.1.4
Chip SOC version: 0.36.2.0
The other unit exhibits NO noise/interference on BT with WiFi on-
OS Version: 7.10.7740.16 <-------------
Firmware revision number: 2424.11.9.2 <-------------
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.9.1
Radio hardware version: 0.0.0.800
Bootloader version: 5.9.0.6 <-------------
Chip SOC version: 0.36.2.0
Both are carrier unlocked 16GB units. As a noobie, I am unsure of how to back down the FW & BL and up the OS version to make the first unit identical to the second and see if the interference issue goes away.
Is there a unique build version that incorporates all of the characteristics of the second phone that needs to be installed on the fiirst phone?
I don't think it's a software/firmware problem. More like the fact that the phone that works is of a newer hardware revision ("silent" update of the radio hardware by Samsung, not reflected in the numbers shown by the phone).
AnnihilatorSC said:
I don't think it's a software/firmware problem. More like the fact that the phone that works is of a newer hardware revision ("silent" update of the radio hardware by Samsung, not reflected in the numbers shown by the phone).
Click to expand...
Click to collapse
I am on my second Omnia 7 now. Waiting to see if this one solves the radio issues I had with data.
However on the issue of bluetooth and wifi.
Pre-Mango I had no problems with bluetooth. After I updated to Mango my bluetooth wouldn't work properly if WiFi was turned OFF. It wouldn't discover or connect to any devices.
Strange problem...
I know there were batches of Omnias with dodgy radio hardware. Altough the Hardware rev numbers didnt change I also suspect an "behind the scenes" change on Samsungs part.
OK here are the Serial Numbers of my 2 units. The problem unit would seem to have a "later" number
OK device: R3UZB61413V
Problem device: R4XZC52489A
If the 5-digit number in the last 6 places is sequential, then the problem device is older, but the R4 and XZ sequences are "higher". Any help.
At least one post on a related topic mentioned that the interference started after an update, and went away when the previous software was restored.
---------- Post added at 05:36 PM ---------- Previous post was at 05:30 PM ----------
Also, this is puzzling to this noobie -
Why won't the 7.10.7720.68 device update to the 7.10.7740.16 version of Mango? The Zune software reports no updates available...
tarzan_nojane said:
OK here are the Serial Numbers of my 2 units. The problem unit would seem to have a "later" number
OK device: R3UZB61413V
Problem device: R4XZC52489A
If the 5-digit number in the last 6 places is sequential, then the problem device is older, but the R4 and XZ sequences are "higher". Any help.
At least one post on a related topic mentioned that the interference started after an update, and went away when the previous software was restored.
---------- Post added at 05:36 PM ---------- Previous post was at 05:30 PM ----------
Also, this is puzzling to this noobie -
Why won't the 7.10.7720.68 device update to the 7.10.7740.16 version of Mango? The Zune software reports no updates available...
Click to expand...
Click to collapse
It reminds me of the farce with the 1.3 and 1.4 rev Focus. A hardware revision that needed specific updates to work.
I do wonder if the Omnias (my original and my sisters - we both had data problems since mango) we have are incompatible with the update.
FW wouldn't update issue
I finally managed to get the FW updates onto the first phone. Restored the FW to CSC_Cetus_Europe_I8700XENJK1 version, and after all auto updates, the phone was now at 7740. Then I manually updated to the even newer Samsung only FW.
BT-wifi interference issue never went away. Thankful for gazelle.com 30-day policy and returned that phone.
Since the phone was going back, I did get the nerve to try the free Dev Unlock procedure for Samsung outlined elsewhere. Worked like a charm and gave me access to Registry Editor Tools and similar.
Related
Bluetooth switches off on our imate jasjam's we have at least 10 of them with this issue. When paired with a car kit they may receive a call through the kit then the next call through the device and when they check the device they find Bluetooth has turned off. To get it to re-enable they need to soft reset the device 3 times out of 5.
They are using 2 different brands of car kits.
After researching my bluetooth issues I found the 3518_09 fix for the imates bluetooth issues.
I have installed this patch on 6 or more imates and had mixed results. All of them were the latest official telstra jasjam rom. Some devices now have better connections to car kits with no bluetooth connection issues and a couple of them are now worse. The bluetooth radio switches off and then won't turn back on. If you reset the device then bluetooth will work again. Basically with or without this patch Bluetooth will switch off randomly on the imates. Some devices behaved better after the install and some worse. Frustrating.
Is anybody else having this issue?
Does Radio 1.41 help bluetooth issues at all?
Thanks
Radio 1.41 will not fix my bluetooth issues. I have read that much in the wiki
I also have this issue.
However it seems to be a problem either when I switch off the ignition with the phone in the car kit or remove / replace the phone on the car kit.
I didnt seem to have noticed an issue in the past month or so but since then its getting to be quite a pain. I have to go back into the comms manager and re-enable it most of the time.
I have an M3100
Operator Version 14.123.1.614
Rom Version 1.23.61.4
Rom Date 07/13/06
Radio Version 1.16.00.00
Protocol version 32.53.7018.01H
Thanks
Have updated my phone
Since running the latest Orange Updater file:
SPV_M3100_ROMUpdate_0407.exe from Orange website.
www.orange.co.uk/business/downloads/SPV_M3100_ROMUpdate_0407.exe
This updated the firmware to:
Operator Version 14.211.1.611
Rom Version 2.11.61.1
Rom Date 03/23/07
Radio Version 1.38.00.01
Protocol version 32.71.7020.12H
This seems to have fixed my bluetooth issues. Also the phone is running much faster.
thanks for the info. is it possible just to take the bluetooth drivers from one rom and use them in another? I see that the 3518_09.cab has a bluetooth driver in it (i assume that's what it is) so maybe that is one of the files to look for. any help?
I have extracted the files from the rom posted above. I am going to try replacing btagext.dll, bthuart.dll & serial_btur.dll.
Hi there,
I have had very few issues with my headsets on WM 6.x devices before.
With my Quantum, I bought a new Motorola Oasis headset and RMA'd it for a new one due to this issue (which hasn't been fixed):
If I am not within 2 feet of the phone, my voice audio quality is terrible.
I can hear just fine. Outgoing voice is terrible.
It can be in my pocket, on a table, whatever. The connection is terrible once it gets out of my shirt pocket.
I have turned WiFi off, data connections off, etc.
Is the bluetooth radio in this phone weak?
I was thinking of removing the metal back and seeing if that helps.
Thanks,
TTFN
Gregg
OK, so this problem is still pretty infuriating.
Does ANYONE have a recommendation about a BT headset that would work acceptably when the phone is in my pocket?
I mean, it disconnects if I put it diagonally across my body.
Maybe my phone is bad? Both the new and old headset seem to perform similarly.
I'm currently looking at the Blueant T1 which appears to have a slightly longer range in some reviews.
I can't speak for headsets, cuz I haven't tried any yet, for any length of time, but I can tell you the Quantum works fine with my Garmin BT-enabled unit in the van -- no matter if the phone is in my pocket or on the console between the seats.
FYI, I'm not the only one with the problem with poor bluetooth performance.
http://answers.microsoft.com/en-us/...formance/c4379403-464d-45a2-8750-e80ca8dc4d4e
It's still a mystery.
My car doesn't appear to fix the problem. I figured I had the ultimate BT headset now!
drtolson said:
I can't speak for headsets, cuz I haven't tried any yet, for any length of time, but I can tell you the Quantum works fine with my Garmin BT-enabled unit in the van -- no matter if the phone is in my pocket or on the console between the seats.
Click to expand...
Click to collapse
I have no problem with Bluetooth range in my Santa Fe, BUT, while I can receive incoming calls without issue, I can only make outgoing calls on the LG Quantum if the screen is unlocked (ie, on the live tiles screen or deeper). That seems like a flaw to me. My old LG Voyager worked while it was in my pocket for both incoming and outgoing calls from this vehicle.
I've tried what settings I think could have an impact, but the "take the phone out of my pocket and unlock before making a hands free call" problem remains.
Any suggestions would be appreciated. Thanks from a noob!
SOLVED?
Just FYI...
I sent my phone back to LG for repair after proving to their tech that it was a problem, and being unable to prove to AT&T it was a problem.
LG returned my same phone to me with the note saying they "Updated The Software".
Prior to sending it, I updated it to 7392 (because that triggers a backup in Zune). Mine was one of the very first LG Quantum phones produced.
The phone came back with 7390 on it and apparently different Radio ROMS.
I tried the phone out after getting it back and the Bluetooth issue is indeed much better. I think they updated the radio ROMs. Unfortunately I don't know exactly what they were when I shipped the phone off.
Here's the new version info (I ran the update to get back to 7392):
Phone LG Quantum (LG-C900) on AT&T.
OS Version 7.0.7392.0
Firmware revision 1.1.3.11
Hardware revision 1.1.0.0
Radio software 1.1.3.11
Radio hardware version 0.3.5.0
Bootloader version 1.5.1.0
Chip SOC Version 0.30.2.0
If I see it right, the Radio ROM version is much different.
The bad part...
The phone will not restore my Zune backup. So I think there is definitely a version mismatch somewhere.
TTFN
Gregg
i have been using my few weeks old (to me) used quantum in my car with minor issues.using the stock rom, volume was VERY low. restoring to an image here then upgrading via zune seems to have worked wonders in my car (alpine iva-w505 with kce-400bt bluetooth module)
then updating my car's bt firmware made it even better.
Could you post the radio / rom versions on your phone after that update (like I did)?
I'm curious where yours is now vs. where LG put mine after the service.
I wonder if I can upgrade my Subaru's BT stack? Hmm...
Os very 7.0.7392.0
Firmware rev 1.1.3.11
Hardware rev 1.1.0.0
Radio rev 1.1.3.11
Radio hardware 0.3.5.0
Bootloader 1.5.1.0
Chip soc 0.30.2.0
Sent from my A500 using Tapatalk
I think the radio ROM version was the issue on my phone then...
If I had done what you did, I wouldn't have had to send it away for service!
My radio ROM was older. I still can't get too far away from the phone before sounding like a Cylon, but it is way way better than it ever was.
And Mango makes the Bluetooth work so much harder that it would have been supremely frustrating to have it not working right!
Thanks for the ROM version post!
I have the DVP (unlocked, with latest updates and FW fix), and every time I connect it to my car's bluetooth, it displays a "1" on the phone and immediately errors out. So it sees the headset to pair, and as soon as it pairs, it changes from "Headset" to "1" on the phone, and the car immediately rejects the phone. I've had no issues pairing my last DVP with the car (this came back on warranty) so I'm out of good ideas.
Anybody have any?
I use this function every day and it works fine for me what's your version software?
Maybe the last update resolve this issue...
OS Version is 7.0.7392.0
Firmware Revision is: 2250.1800.7392.212
Hardware Revision: 112.576.2.0
Any ideas?
maybe mango will fix the issue? why not upgrade. There is no downside.
Does it have problems with other BT headsets?
Hi all
searched for this and while some similar symptoms there doesn't seem to be anything really the same.
I bought a 16GB Omnia 7 in Seattle and I believe it's a Dutch retail item. Got back to the UK, set all the network/regian/language/etc. settings to UK and everything has been cool...except bluetooth.
The phone will not discover nor is it seen by any other bluetooth device. A colleague who bought one at the same time has the same issue.
I'm told that the way to fix this is to flash with a UK retail ROM. Is that right? or are there other fixes?
I've read the update guide and bar selecting the best ROM am happy with the process.
Current versions:
OS version: 7.0.73920
Firmware revision number: 2424.11.2.3
Hardware revision number: 3.15.0.4
Radio software version: 2424.11.2.2
Radio hardware version: 0.0.0.800
Bootloader version: 5.2.1.4
Chop SOC version: 0.36.2.0
i flashed this rom I8700XXKC1_XXKB2 to my orange uk omnia7 some months ao & havnt had any problems what so ever. my mango upgrade has just completed as i type.
robnewton1 said:
i flashed this rom I8700XXKC1_XXKB2 to my orange uk omnia7 some months ao & havnt had any problems what so ever. my mango upgrade has just completed as i type.
Click to expand...
Click to collapse
Interesting - was that to fix this problem for for another reason?
and is there a way to force the mango update?
chrisnic365 said:
and is there a way to force the mango update?
Click to expand...
Click to collapse
Ignore that bit I've done it. Just need to test when the phone comes back up
Bluetooth Problem after Mango Update
Well I got bored waiting for T-mobile UK to do anything so I debranded and forced the mango update.
All seems well except the phone will no longer pair with my car! (BMW)
It sees some other phones.
Any ideas? Will there be another firmware update later? Which component determines the bluetooth level? I now have firmware 2424.11.8.5
Cheers
Rob
Please if anyone has a fix for bluetooth enlighten us all. I have tried everything I can find that might suggest a fix but nothing.
Well since doing the mango upgrade the phone can now at least find other devices but it refuses to connect to anything.
Serious thinking about selling it.
Mine seems fine , had a text conversation with my wife while driving last wee using my old Motorola earpiece . I always switch wifi off before using bluetooth (used to have regular disconecting problems)
roblpm said:
Well I got bored waiting for T-mobile UK to do anything so I debranded and forced the mango update.
All seems well except the phone will no longer pair with my car! (BMW)
It sees some other phones.
Any ideas? Will there be another firmware update later? Which component determines the bluetooth level? I now have firmware 2424.11.8.5
Cheers
Rob
Click to expand...
Click to collapse
Oops - this was just me being a numpty!!!
For some reason deleting the phone (as added on nodo) from the car and then readding worked. Have you guys tried this??
I had to finally send my phone (on Samsung's instructions) back to a company called Regenersis. I had bluetooth problems as well. It would connect to my Audi MMI but would not connect to my Parrot miniSlim head set. They replaced the"board" in the phone. I knew this because when I got it back there was only 8GB memory instead of 16. So, it went back again and the board replaced to a 16GB one. Bluetooth works superfast now and absolutely no problems. So you might want to contact Samsung UK and ask for it to be repaired at Regenersis.
roblpm said:
Oops - this was just me being a numpty!!!
For some reason deleting the phone (as added on nodo) from the car and then readding worked. Have you guys tried this??
Click to expand...
Click to collapse
Well I'd had no bluetooth problems until now...
Was paired with a Jabra unit in my car no problems. Updated to mango and it was working alright until tonight when it refused to connect. Spent ages trying to get it to re-pair. Had to delete the association, reboot my phone and the bluetooth device and they finally re-paired.
Seriously starting to hate this Mango update. Yeh it adds cool features but it seems to have knackered my data connection completely and now my bluetooth is playing up.
Last Samsung phone i ever buy. Had no problems with my old HTC. Can't wait for Nokia.
17-apg said:
I had to finally send my phone (on Samsung's instructions) back to a company called Regenersis. I had bluetooth problems as well. It would connect to my Audi MMI but would not connect to my Parrot miniSlim head set. They replaced the"board" in the phone. I knew this because when I got it back there was only 8GB memory instead of 16. So, it went back again and the board replaced to a 16GB one. Bluetooth works superfast now and absolutely no problems. So you might want to contact Samsung UK and ask for it to be repaired at Regenersis.
Click to expand...
Click to collapse
Where i work , our branch (Glenrothes Fife) doesn't do them as far as I know . Do you know where it went ??
Hi,
I bought an Omnia 7 off ebay which is apparently a T-Mobile uk one (it has T-mob battery cover).
It was already running Mango 7.5 when I got it and I'm so far happy with it but I've had to ditch my Nokia BH-207 headset as you just couldnt hear anything through it as it was so quiet.
I've paired the phone to my TomTom Go540 Live and its a little better but its still really quiet. I've read the threads on boosting the sound levels but cant find anything on boosting just the Bluetooth and dont want to change all the system sound levels.
Also I've not managed to get any updates through Zune and wondered if the updates people are mentioning (tethering update) would fix my bluetooth volume problems.
My phone is running:
os 7.10.77020.68
firmware 2424.10.12.3
hardware 3.15.0.4
radio swr 2424.11.2.2
radio hwr 0.0.0.800
bootloader 4.12.0.9
It also has no T-Mobile uk branding when you turn it on.
Thanks in advance for any help.