Related
ok.. I read a couple of threads regarding this issue but could not find any solutions. one guy said that ak3.3 fixed his problems but 3 have a spv m3100 and I don,t know wich update pack should I choose besides cingular wich doesn't have video calling.
Any thoughts?
Doesn't anybody have the same issue and managed to solve it?
I had the same issue when I upgraded to WM6, I fixed it by installing the GPS radio ROM. This fixed it straight away.
In installed the latest 1.35 ROM and that did not fixed it and even with XDA live that did not work. Where can I find the GPS Rom?
andrei318ti said:
Doesn't anybody have the same issue and managed to solve it?
Click to expand...
Click to collapse
My 8525 was disconnecting from my car constantly after getting the phone a few days ago. My TyTN never had this problem. Even after installing the exact same ROM onto the 8525 that was on my TyTN I still had the same problem.
Basically, after a minute or two of being connected to my car the bluetooth on the phone would turn off. It didn't just disconnect. It turned off completely. This phone did it just like the Treo 750v (very unreliable phone by-the-way) did.
The problem appears to have gone away now that I have installed WM6 on my 8525. I have not done anything special to get it working aside from installing the LSVW WM6 ROM. It is definitely worthwhile to give it a try.
I believe that 1.35 is the "GPS enabled, but not initialized" rom.
OJ2000 said:
I had the same issue when I upgraded to WM6, I fixed it by installing the GPS radio ROM. This fixed it straight away.
Click to expand...
Click to collapse
I had it fixed by changing the registry values for bluetooth power saving. Upgrading to VM6 and to radio rom 1.35 (gps enabled) bringed back the problem... now I cannot find anymore what registry value I had changed...
stepir said:
I had it fixed by changing the registry values for bluetooth power saving. Upgrading to VM6 and to radio rom 1.35 (gps enabled) bringed back the problem... now I cannot find anymore what registry value I had changed...
Click to expand...
Click to collapse
Ohhh....please try to find them because I searched high and low and still no solution.
Try this:
http://forum.xda-developers.com/showthread.php?t=245887&highlight=bluetooth+power+saving
Ok I tryed the small fix on that link and did not work at all. I also inslled WM6 LSVW and still nothing. Any other ideas?
Try this: "jetware.hands-free.extension.1.24".
Installing the leaked Cingular ROM fixed the problem for me. Prior to this, it would connect briefly, then disconnect, and would come and go, but mostly would not connect. Now, every once in a while, it disconnects very briefly, but for the most part is solid.
Tryed jetware but still no go. Any other idea? doesn't anyone that has a hermes use a car handsfree bluetooth system? From what I know all devices suffer from this?
Nothing? Hasn't anybody found the solution to this problem? From what I read it happens to almost all hermes devices.
Yes, had the same problem.
Have a SPV M3100 with the Audi A4 Bluetooth (part of Gen II GSM Prep).
My old MDA Vario worked flawlessly.
SPV3100:
1. Pairs and makes / receives calls.
2. After 10-15 Mins calls are not routed through car kit.
3. When making / recieving call after 10-15 Mins, handset thinks its connected to handsfree (headset symbol in phone dial pad) but car does not pickup call hence no handsfree and no sound in handset ear piece!
4. Occasionaly, handset reconnects to car handsfree automatically on an incoming call.
5. Connection of in car charger SEEMS to improve realiablility.
6. Switching Bluetooth off then on on the handset will initiate a new connection that again works for 10-15 Mins.
Mark
temoore said:
Installing the leaked Cingular ROM fixed the problem for me. Prior to this, it would connect briefly, then disconnect, and would come and go, but mostly would not connect. Now, every once in a while, it disconnects very briefly, but for the most part is solid.
Click to expand...
Click to collapse
I get the problem with the new rom also, have been using it for weeks now. The new ROM does NOT resolve the issue, at least with the Acura HFL system.
So it seems that there is currently no fix to this issue.
bsica said:
I get the problem with the new rom also, have been using it for weeks now. The new ROM does NOT resolve the issue, at least with the Acura HFL system.
Click to expand...
Click to collapse
Well, it did resolve it on my '07 Audi Q7.
I tried to contact HTC and this is what I got
Thank you for your enquiry. An IMEI check of your device indicated that it is a network branded phone.
IMEI:? 357719003647231? Network: Orange Romania SA
Unfortunately we do not offer technical support for network branded handsets, as both software and hardware can be altered by the network provider.
Please contact your provider for any support that you might need, including repairs and software updates.
Click to expand...
Click to collapse
Can anyone with a TyTN contact HTC and ask for a solution?
Thanks temoore,
Looks like I need to get my boss to upgrade my car from A4 to Q7 to get the phone hands free to work.
It just might work.......;-)
Hi all,
I'm running original WM06 ITA on my x7500 and I'm experiencing this problem:
when I receive a call I can't answer with my BT headset because X7500 BT is turned off even if it was on, so that I have to activate it again. So the problem is that X7500 BT turns off by itself very often in a day. How can I solve this problem? Any fix available?
THX so much!
hi
i have the same problem. this thing happens 2-5 times a day to me. the wicked thing is that somtimes it works perfect 1 or 2 days and when you think no everything is fine 'pop' its there again. fact is that bluetooth simply disappears, the indicator on athena is still blinking blue and the commanager tells bt is on, but my bt-headset (and other devices) signals that the bt connection is gone, also other devices cant find the athena any longer. i have to disable/enable bt in the commanager to get the functionality of bt back. i was thinking about returning the device for repair, but fearing the discussion of not using the original rom (the one with the superugly optical improvements of the provider ). and because maby it's a rom problem. my config is:
htc rom 2.21.407.1 (07/18/07) with extrom:2.21.407.101.
3 bt-headsets 1. sony hbh-ds220, 2. moto s705 and moto ht-820. all 3 are working fine with my universal but having these problem with the athena.
madbird
Hi...so we have the same problem...
I have the original HTC ROM just restored on my device and I have the problem. I read about it somewhere, other people with same problem but I can't remember where...
yes we are not alone i found serval posts on the net for htc and other brands like these:
http://forums.wireless.att.com/cng/...thread.id=27495&view=by_date_ascending&page=1
http://www.howardforums.com/showthread.php?t=867111
but no solutions. the only meaningful thing was for wm5, there is a fix of the bluetooth stack by microsoft (http://support.microsoft.com/?scid=kb;en-us;913683&x=13&y=14) but i did not found one for wm6.
mad
Hi guys.
I'm sorry to say that I had, a long while ago, the same problem with my Universal, and after a whole lot of tweaking, tinkering, and kinky massaging, all that was left to do was to have the device replaced. It definitly was a hardware problem, alas... :-(
I've had mine almost 4 months, stock 7501 ROM, and no problem like that ever. I leave BT turned on all the time. Sounds like a hardware problem.
been there done that fixed that
hi all,
yes, until I found the coolest und most functional BT headset, the cheapy prior ones caused same faults, even to the point of a hard reset ... why, well
no help to be found, just the notion of thinking and knowing, that the cheapy hardware out there was casuing it, not the htc.
example, some devices go into a kind of sleep mode and disconnect if not used, then while the htc still thinks its connected, it gets no reply from your other BT device. Take many SW packages or HW devices on your PC even, unplug the network and u´ll see, even they have unforseen problems ...
have fun, try HW makers like HAMA or Samsung, they rarely disappoint.
ollli
Aaaahhhh, I'm not alone.
Same problem here, but ONLY afair with WM6 (I'm using WM6, T-Mobile Germany). I can't remember, that I had this problem with the original T-MOB WM5 ROM.
Regards
Andreas
ollli3d said:
hi all,
yes, until I found the coolest und most functional BT headset, the cheapy prior ones caused same faults, even to the point of a hard reset ... why, well
no help to be found, just the notion of thinking and knowing, that the cheapy hardware out there was casuing it, not the htc.
example, some devices go into a kind of sleep mode and disconnect if not used, then while the htc still thinks its connected, it gets no reply from your other BT device. Take many SW packages or HW devices on your PC even, unplug the network and u´ll see, even they have unforseen problems ...
have fun, try HW makers like HAMA or Samsung, they rarely disappoint.
ollli
Click to expand...
Click to collapse
hi
i dont know if you read the post's above, but if you do you will see that the pda is turning off the bt, so it dont matter if you use one of the 'fantastic products' of hama (yes i also read your other 2 'advertising' posts of your overall 3 for them ). or any cheap crap stuff from sony or motorola like i do.
anyhow to came back to the real problem, i called my provider today and after explaining the problem, they suprise me with a complete hasselfree swap of the device to a new one in the beginning of the next week. when i get the new device i will test it first with the rom that installed, and then switch to the htc rom again to see if the problem returns again, i post the results here.
bye mad
Yeah, I think they're probably aware there's something wrong with some bluetooth chips, both on the Athena and Universal....
hi,
with wm6,
i have tested a BT 1.1 headset (Conceptronics) and works fine, without problems.
also, i have tested 2 BT 1.2 headsets (LG Style-i and Supertooth Nano). In the 2 cases, i have your related problems.
in my opinion, wm6 has a problem with the headsets that implements the 1.2 protocol.
all the headsets works fine with wm5.
regards
I have same problem with HTC Advantage running WM6 with LG Style-i headset ...
With my LG Style-i it keeps disconecting but with my SE BT headset it works fine (PK 3.0 Dual ROM) so in my case the BT on the phone doesnot turmn itself off, just has problems connecting.
Someone sugested a diff radio ROM might fix it - if so, does anyone know which radio does not implement the 1.2 protocol?
I'm using 1.47.51.00
hi there
i'm using my replacement athena for nearly one week now, and had not a single 'shutdown' of bt, not with the se ds220 nor with the moto 705 headset. i use the official german tmobile wm6 roms and not the htc version i used on the replaced athena. so it is not totaly clear if the change of the device or of the rom is making the difference, all other software packages are installed again. it also seems that the system is more stable overall in my every day usage, but that might be only my personal feeling.
mad
*EDIT* one more thing i noticed now is that when a call came in the sound is now played in the bt headset. before the sound came out of the speakers of the athena, and the bt headset only play its standard ringtone. seems that now everything is the way it should be .
BigDede said:
I have same problem with HTC Advantage running WM6 with LG Style-i headset ...
Click to expand...
Click to collapse
hi,
i' sure that the bt problem is due to the radio rom. i have the 1.38 radio rom and no problems with lg style. please, install it and test and report the results.
regards
bartito said:
hi,
i' sure that the bt problem is due to the radio rom. i have the 1.38 radio rom and no problems with lg style. please, install it and test and report the results.
regards
Click to expand...
Click to collapse
I have the 1.38 Radio version and I have the problem which is Bluetooth turning off by itself when using LG Style-i
ok, the problem is wm6
BigDede said:
I have the 1.38 Radio version and I have the problem which is Bluetooth turning off by itself when using LG Style-i
Click to expand...
Click to collapse
Did somebody tried to go through these update from Microsoft for WM6 ??
http://www.microsoft.com/downloads/...76-ff8d-460c-b454-6c487fd4c7d9&DisplayLang=en
http://www.microsoft.com/downloads/...c1-f0f4-4fd6-9366-b61e0ab59565&DisplayLang=en
http://www.microsoft.com/downloads/...5f-782b-4378-a228-f18af8c59aa3&DisplayLang=en
hi spiderman ,
i don't have teste (i have wm5) but the description seems don't have relation with bt stack procedures.
regards
Hardware or software
It's 4 months since last post and wondering if someone found a solution?
Hi,
I go into bluetooth and search for my devices on my Omnia 7 but it seems to be stuck on Searching when I try and search for my MW600. Anyone experienced anything similar?
So far I have tried it with a couple of different headphones from SE and Plantronics but still no joy...
Jag har precis samma problem som dig med samma headset plus att min hörlursingång verkar glappa
Exactly the same problem, bluetooth worked for about a month but the quality was terrible. As time went by it got harder to pair with the car and now it just sits there searching...
I have the same issue, struggling with a lot of Bluetooth problems at the moment. I also have a MW600!
I can get it to pair with the MW600 if I turn WiFi off. After pairing it seems to work fine with WiFi back on.
With various power cycles, entering and leaving flight mode etc. I can get it to see some devices. Can't get it to pair with my car kit though no matter what I do, and that's the only thing I really want to pair it with.
It seems to be a common issue with Samsung Omnia 7s and Focuses. There is a blog post that google finds where a guy took his phone back and swapped it for another one, which then worked with all the devices his original didn't. One of the commentors then declared that upgrading the firmware to JK1 also sorted the issue. I promptly did this, voiding any chance I had of taking the device back to get a new one. It didn't work, so I'm stuck. The commentor has since come back and said it didn't fix the issue. Thanks for that .
I have an MW600 and I use it with no problems at all. Works perfectly. I have it paired with both my Samsung Omnia 7 and my old Sony Ericsson W610i.
The first pairing took me a while (some pairing codes blah blah), but after that, it's been really smooth. Just switch on bluetooth and the MW600 and they are automatically connected.
Of course, the song name etc does not show up on MW600's display -- I think that's restricted to Sony phone (my old W610i does that perfectly!).
Hope this helps.
I believe based on other peoples experiences there is a Bluetooth hardware problem with early examples of the Omnia 7. You probably have a later one where everything is fixed.
Oh and the reason the MW600's display doesn't show any info is because WP7 only supports version 1.0 of the AVRCP profile, so track info is not transmitted. I've used the MW600 with my old HTC Diamond and Touch Pro2 and got the track info to display. I'm hoping the profile will be updated by Microsoft at some point.
Supported profiles: http://support.microsoft.com/kb/2449475
Well, I jsut got a new 16 GB version last week and I have bluetooth problems as well. even after Nodo they still exist. I have a Parrot Minislim kit and my phone will find it and try to connect. I enter the PIN and hit "done" . It then tries to connect but doesnt. AM bringing it to a service centre tomorrow and will see what they do there.
Update on Bluetooth
17-apg said:
Well, I jsut got a new 16 GB version last week and I have bluetooth problems as well. even after Nodo they still exist. I have a Parrot Minislim kit and my phone will find it and try to connect. I enter the PIN and hit "done" . It then tries to connect but doesnt. AM bringing it to a service centre tomorrow and will see what they do there.
Click to expand...
Click to collapse
Well, I brought it to the Carphone Warehouse who are the service agents for Samsung and guess what , they cannot send it back for repair because they have no "PLU" in their system for this model citing that they do not offer it in their catalogue. They have told me this 2 weeks after I left in in with them. Now, I have got to get it back from them and send to Samsung myself. Like others here I must have an early model because it is doing the same things, sometimes connecting to my Parrot MiniSlim kit and sometimes not. I bought a 16GB version from Germany because I wanted an unbranded and unlocked version with this amount of memory.
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 ??
Dear community,
Having read, that the Sony Ericson Bluetooth Headphone (MW600) works with a Samsung Omnia7, I finally bought one.
But: When I try to connect/interlink these to devices nothing happens. My beloved Omnia7 only stays in "searching mode", finding no other Bluethooth sources.
I know that in august last year, it found at least my older Cellphone (but couldnt connect), but now it doesn't detect anything.
What can I do?
OS: Mango 7.10 (7740)
Diagnosis:
PDA I8700XXKI4
Phone: KI1
CSC: KI4
Bluetooth S/W: 0.0.1
Bluetooth H/W: 0.0.1
Bluetooth Mac: 7847 (and so on)
try updating to 8107 and check again
Hey Blaster,
thanks for the reply. I updated today (TMobile-Germany just offered Update to 8107 this morning). But unfotunately nothing happened. I'm going to contact the TMobile Customer-Service. Maybe it is a hardware issue.
Edit: Just found out ... I'm not the only one: http://forum.xda-developers.com/showthread.php?t=1293248&page=2
rednex2 said:
Edit: Just found out ... I'm not the only one: http://forum.xda-developers.com/showthread.php?t=1293248&page=2
Click to expand...
Click to collapse
Yes there is a big problem with bluetooth in omnia 7
http://forum.xda-developers.com/showthread.php?t=1441902
http://answers.microsoft.com/en-us/...7/c0e880dc-91c8-4a31-b5b9-96185707e0e1?page=3
Hey rustemka,
so, looks like nobody knows if the problem is related to the hard- or to the software...
This topic may be closed, as I will join the other threads!
Thanks to all!
rednex2 said:
Hey Blaster,
thanks for the reply. I updated today (TMobile-Germany just offered Update to 8107 this morning). But unfotunately nothing happened. I'm going to contact the TMobile Customer-Service. Maybe it is a hardware issue.
Edit: Just found out ... I'm not the only one: http://forum.xda-developers.com/showthread.php?t=1293248&page=2
Click to expand...
Click to collapse
what happens to bluetooth is not really clear, my phone was T-mob de too but (fortunately) mine works and pairs with my headphones, the only problem i have is, when playing a video i hear the sound through back speaker, and still remains with 8107 update
@ DJ: I've read in other forums (not sure, it might even be the answer.microsoft-forum) that this is a general WP7-issue.
I'd glad, if only I could listen to music via BT.
I don't think it's hardware failure... rather incompatability.
My 1st Omnia worked perfectly until Mango. After I updated it my data connection stopped working right as did my Bluetooth. It was the same on 7720 and 7740.
My replacement Omnia on 7740 works fine... It seems odd that hardware would fail exactly at the time I updated it. My sisters Omnia (also purchased at the same time) also had the same problems after the Mango update.
I suspect Samsung changed components (as with the rev 1.4 focus) but didn't announce it and these variations are causing problems with the firmware.
This is just my opinion however.
Turn the wifi off, that worked for me and Nokia BH-111.
It was stuck in "searching..". After i turned the wifi off, it found he headset instantly. problem is, now i can't use bluetootha dn wifi at the same time, ff/rewind doe not work and playback is a bit patchy. i believe i've read it's a hardware related problem and i will try to score a replacement.
turning WiFi off, didn't work for my Omnia7.
I even bought a Samsung HS3000 BT-Headphone, for the samsung-customer service guaranteed compatibilty, but nothing changed. Bluetooth ist still "searching".
Going to replace it as well.
me too
this seems to be a big problem with the omnia 7, as both myself and someone i work with have the same problem. supposedly (not sure of the authenticity of this one, so please take with a pinch of salt) the omnia 7 was designed to only speak to other omnia 7's for some reason, as if samsung thought bluetooth file sharing was gonna be possible with wp7. seems vaguely (only vaguely) plausible, but just thought i would add my tuppence.
same
i have motorola s9 bluetooth stereo headset, and worked since nokia n95, throught varius wm (htc samsung sony ericcson) phones, and android too... now with omnia 7 was not working well, but when i disabled wifi started to work again... i don't now why, and i've not tried bluetooth and wifi at the same time with other devices (i use bluetooth only on car and when i go running)... is it normal?
No, normally WiFi shouldn't interfere with BT as far as I know- but this seems to be common with the Omnia7.
@chrisrobinson: The Samsung support guaranteed, that Omnia7s work with their HS3000. Accordingly the Omnia7 should speak with other devices than other Omnia7s. But mine doesn't.
rednex2 said:
No, normally WiFi shouldn't interfere with BT as far as I know- but this seems to be common with the Omnia7.
@chrisrobinson: The Samsung support guaranteed, that Omnia7s work with their HS3000. Accordingly the Omnia7 should speak with other devices than other Omnia7s. But mine doesn't.
Click to expand...
Click to collapse
Mine was slightly different. It only worked when WiFi was turned ON. It didn't work if WiFi was OFF.
something happend a few days ago. Since than, the "alphabetic character-tiles" on the screen with the list of all the installed apps appear like "border in theme-colour, background in beackgroundcolour, character in theme-colour". . . and:
even my bluetooth started working again (only if wifi off, ... of course).
It now finds my MW600 Stereo Headset. And connection is established.
BUT: I can't listen to music. I can read the title of the mp3 on the headsets display, turn volume loud on both devices, but no sound at all. hmm
I've given up on my BH-111.
The headset works fine with my laptop and nokia 5230 and nokia n97, but not omnia. Too bad, would have been nice for running and such.