I have upgraded to the new O2 Rom 169 and all seemed ok, until I started to install my bluetooth head set.
Since I upgraded my radio ROM to 1.03 I have lost the connections to my headset.
Prior to the upgrade it worked perfectly, now the recieve functions just will not work.
I have down graded to the radio 1.00 ROM but the same thing is happening. So the upgrade seems to have corrupted something more important.
Can anyone help here?
Downgrade to previous ROM
I have now downgraded to the previous ROM 1.11.162WWE, and that seems to have solved the problem.
I have installed the Radio ROM update and that seems to work OK now, so I will stick to this for the moment, unless someone has any better ideas!
Hello,
I had the same problem. It seems, the old bluetooth software won't work with the new radio rom. I tried my bluetooth connection before restoring my old stuff from backup, and it's ok. I didn't have any serious things in my backup, so I reinstalled my software from install cd's - sorry, I had no time to figure out, wich software causes this issue, but hope this information will help you.
Z.
i also having problem with my bluetooth but I cant say the problem is from new radio ROM or others because i dont know the real cause. A message display and wrote
"Sorry! Bluetooth can no longer be used because the licence is expired"
"BDA ff:ff:ff:ff:ff:ff: Key:E3E534E19B3E8214C543A73C0A8B9A9074DD3B1753515CD8"
after that, bluetooth will off automatically.
I have found since the upgrade to the new radio, thanks PUG.
That my Handsfree and Headset Bluetooth issues have lessened.
A few little glitches but will be on the outlook for another patch or upgrade in the future :roll:
Hmm,
I have radio 1.00.00 version with t he original Asia ROM and something funny has happened:
Since the beginning, I successfully connected to Logitech and Hello II BlueT headsets + a generic car BT handsfree.
I had to perform a hard reset after one of my progs messed the registry and reinstall everything (less the troublesome prog <g>).
Since then, the BlueT handsfree does not work properly: I hear the ring but there is no volume control from the headset and I hear nothing + mike does not work. The rest of the BT conections work flawlessly, except for some rare disconnects from my BlueT RBT-2001 GPS.
The story in this thread is not encouraging but one thing is clear - the BT problems that I have are with the original radio and EROM and not after an upgrade. I have no clue what all this means except for the fact that tere is something quite problematic w/ the Xda IIi BT connectivity that I didn't have w/ any of my previous PDAs.
I thought to u/g the radio version only but decided to go for a full u/g (less the O2 stuff), hoping that my BT problems will go away.
Please correct me if I'm wrong - should I go ahead with the PUG O2-less upgrade or should I keep the old (but clearly buggy) versions?
Maybe all the problems that we have are connected to specific manufacturing HTC batches? Has anyone researched this? Is there any info correlating between problems and Xda IIi serial numbers?
Best regrads,
Al
Related
Hi,
I have radio 1.00.00 version with t he original Asia ROM and something funny has happened:
Since the beginning, I successfully connected to Logitech and Hello II BlueT headsets + a generic car BT handsfree.
I had to perform a hard reset after one of my progs messed the registry and reinstall everything - NOT from a backup but from scratch (less the troublesome prog <g>).
Since then, the BlueT handsfree does not work properly: I hear the ring but there is no volume control from the headset and I hear nothing + mike does not work. The rest of the BT conections work flawlessly, except for some rare disconnects from my BlueT RBT-2001 GPS.
The story in this thread is not encouraging but one thing is clear - the BT problems that I have are with the original radio and EROM and not after an upgrade. I have no clue what all this means except for the fact that tere is something quite problematic w/ the XDA IIi BT connectivity that I didn't have w/ any of my previous PDAs.
I thought to u/g the radio version only but decided to go for a full u/g (less the O2 stuff), hoping that my BT problems will go away.
Please correct me if I'm wrong - should I go ahead with the PUG O2-less upgrade or should I keep the old (but clearly buggy) versions?
Maybe all the problems that we have are connected to specific manufacturing HTC batches? Has anyone researched this? Is there any info correlating between problems and XDA IIi serial numbers?
Best regrads,
Al
Guys
Since the upgrade, everything has been working great, with the one exception that the bluetooth pairing with my BT car kit (Parrot CK3300) keeps dissapearing from the XDA.
It works for a few days (using TomTom 5) then it suddenly dissapears, and I have to set it all up again.
Any ideas?
Ta
they is quite a few of us in the same boat, i have tried a few things but am stump now just waiting for parrot to release a new firmware for the ck3300
Thanks
Paul
Try to upgrade Radio to 1.11 , it's responsible for BT too.
Has anyone any experience of this while using Radio 1.11?
This all worked fine until after the ROM upgrade, so is it likely that the Parrot will need an upgrade?
It works ok for a few days then the XDA suddenly bleeps when it tries to connect with the car kit, then there is a dialog box on the XDA screen asking for the passcode to pair up..., I've put the password in (1234), but it always fails... then thats it ... pairing lost
Any clues anyone... this is really starting to frustrate me :x
Ta
1.11 fixes it, but...
When I upgraded from the stock O2 ROM to the T-Mobile one, I found that when ever I switched off my GPS unit, I needed to re-pair it for it to work again. Upgrading to the 1.11 Radio Rom did fix this. Never had a problem with headsets.
But I've also been having some weird power problems - battery going down by 10%+ an hour. Mostly it turned out to be on days when I used wifi in the morning - I'm pretty sure using the new radio dialogue didn't actually switch off the wifi radio when you disconnected. 1.11 does fix that. But also sometimes switching off the phone didn't actually switch off that radio, and power would dissipate way too fast with nothing supposedly on. Doing a soft reset always allowed me to leave it over night and only see 1-2% power gone.
So I've just backed down to the original radio ROM from the original O2 installer. I'm hoping this will solve all my problems, at the cost of the less resilient changeovers from UMTS to GSM.
Ta,
Mark.
i think i have cracked this, my phone has now been connected to my ck3300 for 5 days solid now
here is the post on the parrot forum
http://www.parrot.biz/forums/english/viewtopic.php?id=813&p=4
its at the bottom
Paul
i think i have it pegged have another look at the parrot forum
ok here is yet another update on things.... this is a very strange one. if you enable the device lock start\settings\personal\lock
Prompt if device is unused for 16.7 hours
set simple pin
the phone and the parrot device keep there pairing with no problem at all i have been testing it for the last 48 hours
if you disable the above it loses the paring straght the way.
strange is they anyone else who can try this
Thanks
Paul
I'm using a Parrot R N B, but I have experience the same problem. I have also upgrade to the new radio version, and again the same problem. In fact I can't reproduce the error in a controlled way. It happens from time to time. But more of the time, the Universal connect again to the parrot only assigning again the Parrot as the headset in the Bluetooth manager.
My try now was to install the buzznet.dev cab attached. I'm trying also what buzz said: Do not use the power button to put the Universal off, only close the lid.
I'have 2 days without problems with the parrot. I'll post an update if this also fail.
what parrot do you have? i have a ck3300 running version 1.14d if you can try the above trick and let me know... i could reproduce the error ever time, just connect up 3-4 times and then it would fail..... have not had to worry about the power button trick.
Paul
Mine is RHYTHM N'BLUE, and with this last trick I told you, I add a new day without problems. Today I have started and stopped the Parrot 6 times and always work perfectly.
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 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?
Hello all. This is my first time posting a new thread although I've been lurking around here for a while soaking up all the information from this wonderful site. That said, I have been researching my problem for days now both here and on google and have found no solutions that work. So I'll see if there's anyone here who can help. Here goes....
I have recently flashed DCD's 3.2.6 ROM on my Verizon XV6800 and it works great (love the aGPS too, Thanks GC14) in every area but my car. I have a 2004 Audi A4 with the RNS-E Nav system with integrated bluetooth. Before I flashed to DCD, I had the original stock ROM (2.09.605.8 with Radio 1.30.00) which gave me full functionality with Jetware Mobile (Phonebook and Recent, Received & Missed Calls all transferred). Now, with DCD, it'll only connect to the car and won't transfer anything. If I try to load Jetware, it'll just lock up my phone while I'm connected to the car. Thanks in advance for any help you can provide.
No one else has this problem or a fix for it?
TGabriele said:
No one else has this problem or a fix for it?
Click to expand...
Click to collapse
I wish I was rich enough to afford such a car, then I could maybe help you out. LOL
But I would gladly accept such a car as payment for figuring out your problem.
Nevermind that the car is an Audi. Does anyone else have this problem with a factory BT system that transfers the phonebook to their car.
I had this same issue on my X3 and it seemed to be the way the PPC wanted to transfer the phonebook was by using some file transfer protocol the car did not understand. I could sync it and make and receive calls but no phonebook. Took it to the sprint store and we tried a blackberry and a standard moto handset. The blackberry did not sync the phonebook either but the standard moto phone did. I don’t think it’s possible based on the profiles in the car so I gave up on the phonebook. Try changing the bluetooth stack in the rom, you will have have to make your own rom and beware of the stack you use to make sure it is one for your phone.
I flashed DCD's rom using the kitchen, so making a custom rom from there is no problem to me. What I'm not sure of is how to change the bluetooth stack. I thought it is part of the hard coding for the OS? If you or someone else reading this thread has any information on this or can point me to some info on this it would be greatly appreciated.
I have the 6800 with DCD 3.2.6, and an Audi, with full phonebook transfer so I'll try to help you out:
1. Which 6800 radio are you using? I have found 3.42.50 to be the best as far as Audi bluetooth compatibility is concerned.
2. Jetware will not work with WM 6.1 on the 6800, but you don't need it, since 6.1 included phonebook transfer enhancements.
3. What version of Audi software are you at? There have been several releases since your year. You should be able to get more info from www.navplus.us and of course from your stealer.
4. You do have your bluetooth settings set for "discoverable", right? And, (I don't know why this is the case) it seems when OBEX is on, the phonebook and other items transfer quicker.
If you have the 6800 radio and Audi software updated, you should have no problem. Jetware is no longer necessary.
1. I am using radio ROM 3.42.50
2. The reason I loaded Jetware is to have it sort my contacts by Last,
First. Is there another way to do this?
3. I am running sw0200 on my RNS-E, but was considering moving up to
sw0260.
4. I haven't tried this, but I will.
Lately I've also had the issue where if the phone is connected to the car for a while, the bluetooth on the phone will shut itself off and not turn back on until I do it manually. I'm beginning to wonder if I should just hard reset and start from scratch. Any ideas? Thanks in advance.
I'm sure there's a reg tweak for listing First name first in contacts. Hunt around here or at ppcgeeks. If you want to stay on 6.1 jetware will not work (unless they release a new version).
Definitely update the Audi software to the newest version.
DCD has done nicely fixing power settings in the last few ROMS to solve the bluetooth shutting off issue, although when memory gets very low, it may still happen. You must have some other program or process running that sucks up memory if you are still experiencing this.
It never hurts to hard reset, as long as you have the time.
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
TGabriele said:
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
Click to expand...
Click to collapse
I'm running an after market HU (Pioneer AVH-P4000DVD) and DCD's latest ROM, and Jetware works fine on mine. Just re-transfered my phone book earlier today....