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
Dear Xda's, i have a problem and i need help! I would like to know if there is anyone that knows a rom in which the w100 remote control works perfectly? Since all the Roms that i have tried lately (Dutty, L26, UDK) fail misserably when i try to make to make the remote work. They all af the same problem that they just dont recoqnise the remote, if i plug it in, the sounds still comes over the speaker instead of the headphones.
I also tried the drivers on each rom but they fail to install since its not necessary accourding to them. I have tried extracting the drivers and install one of the seperate drivers but they eather cause my touchscreen not to work or my sound disappears.
I've used the search btw and googled, but after 3 nights for searching and trying i havent found anything so far.
If someone knows a rom, driver or anything that works, please say it here since im gettin a bit frustated. Thanks!
Bump, anyone plix?
Just gonna do smooth bump again since after a month of trying still no succes. HTC isnt responding with an answer so my only hope is here!
L26 KaiserDiamond Throttle Launcher Beta 6 works partially
I have a Kaiser (tilt) running this ROM and the sound is OK. Volume control pops WMP (I use S2P) - mute pops Audio Control and I did not have a chance to test the phone funcitons. But at least I can liste to music
Did you try the original HTC Tytn II ROM posted somewhere in Kaiser ROM development ?
I hope this helps.
Hi, I am running JACMan 1.62 (a great build) with the latest radio and spl. Recently i purchased the HTC Wired Remote rc e100. when i tried to install it, i get an error message telling me tat the latest driver is already installed. Needless to say, the wired remote does not work. I tried to use an app called toggelheadset, but this only allows the music to come through and does not allow the control function of the wired remote to be used, defeating the purpose of purchase. I was wondering if anyone else had this problem, and hopefully someone might have a solution that they could share.
Just quickly looking, it seems people with other HTC phones have the same problem
http://forum.xda-developers.com/showthread.php?t=336902
Is this supposed to work with the Dream? Did HTC themselves say it would work, or just some reseller said so?
Not to mention you are running a modified ROM, so I don't think it should be suprising if you find hardware that won't seem to work, since said hardware has been designed/tested on stock ROMS.
Hello buddies,
this thread is about some strange behavior of bluetooth with current energy roms. details follow...
why a new thread?
I decided to start a new thread, because it leads to nothing to discussing this topic in the main thread ... found some people who shares my sorrow, never the less there was a lot of users who hit the answer button on page 1 and report "problem xy" or "hell yeah what a nice rom"
what is the problem?
I'm not able to pair my TouchHD with my car's Hands Free system. A2DP works fine, but when I turn on the Radio Unit a small blue headphone symbol blinks in the statusbar of the phone - no pairing succeeds. If I switch to BT audio, a black headphone symbol stays resident and the media player opens for playback, so A2DP works. Installing SIM access profile on roms without built in rSAP or other various tools in addition doesn't make it work. [see "what have been done" section!]
Just used the latest MIRI-Roms (discontinued) and it works like a charm for me. After initial setup, Hands Free (version 1.5) and Wireless Stereo where installed and activated - Serial Port left out unchecked. Then a popup message informs me, that a BT-Device is trying to access phones phonebook remotly - all went fine.
as reported by other users, this behavior occurs since ~may versions of energy roms...
about the environment
Using energy's rom on TouchHD [Blackstone] T8282 [BLAC100 32M]
flashing with USPL
phone's SPL: stock SPL-1.54.0000
radio: 1.12.25.16D3 - don't see a reason to update
protocoll: 52.60.25.33U
carrier: O2 GERMAN
what have been done so far?
I've tested the pairing of my device in various cars
tested with my Renault Megane 3 integrated car kit (arkamys audio / parrot)
tested with a 2010 Toyota Prius car kit
tested with a subaru 2010 car kit
tested with Blaupunkt Toronto 400 BT head unit by phitsc
I've tried programs, suggested by the xda community
installed Bluetooth_SAP_Profile.CAB
installed BT_SAP.cab
installed Gooru_Sense_BT_A2DP_Fix_Cab_by_JVH3.CAB
installed HeadsetFix.cab
installed JetBTHFExt_1.40.CAB
reg-tweaks on "HKLM\Software\Microsoft\Obex\ObexServiceMask"
roms tried
Miri_WM65_21891_Premium_Manila_2.5_V20.0_NoHtcMessaging.rar
Miri_WM65_21893_Premium_Manila_2.5_REV22.0.rar
Energy.BLACKSTONE.23563.Sense2.5.Cookie.HomeTab.Apr.23.7z
Energy.BLACKSTONE.23566.Sense2.5.Cookie.HomeTab.May.01.7z
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.16.7z
Energy.BLACKSTONE.21903.Sense2.5.Cookie.May.16.7z
HD_Miri_6.5.X_23541_SENSE25.rar
Miri_WM65_21893_V38.0_Premium.rar
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.22.7z
(green indicates a working rom)
dear community...
please use this thread wisely for recommendations or suggestions on this topic. keep this thread a productive discussion. if you have a contact to NRGZ, feel free to report this thread, cause my afford to reach him fails.
So I hope we can figure out, why it does'nt work as it should to...
kindly regards, FS
Hi,
I have the same problem with my Touch Pro and my Megane 3.
I have to switch back to an older version of the rom then..
Hi,
I'm using Energy ROM Titanium 18may.
Radio 1.17.xxxx
No problem here with BT of my car stereo.
I had this problem untill I delete the old pairing on the car BT.
After this, the phone pair great
firespawn said:
Hello buddies,
this thread is about some strange behavior of bluetooth with current energy roms. details follow...
why a new thread?
I decided to start a new thread, because it leads to nothing to discussing this topic in the main thread ... found some people who shares my sorrow, never the less there was a lot of users who hit the answer button on page 1 and report "problem xy" or "hell yeah what a nice rom"
what is the problem?
I'm not able to pair my TouchHD with my car's Hands Free system. A2DP works fine, but when I turn on the Radio Unit a small blue headphone symbol blinks in the statusbar of the phone - no pairing succeeds. If I switch to BT audio, a black headphone symbol stays resident and the media player opens for playback, so A2DP works. Installing SIM access profile on roms without built in rSAP or other various tools in addition doesn't make it work. [see "what have been done" section!]
Just used the latest MIRI-Roms (discontinued) and it works like a charm for me. After initial setup, Hands Free (version 1.5) and Wireless Stereo where installed and activated - Serial Port left out unchecked. Then a popup message informs me, that a BT-Device is trying to access phones phonebook remotly - all went fine.
as reported by other users, this behavior occurs since ~may versions of energy roms...
about the environment
Using energy's rom on TouchHD [Blackstone] T8282 [BLAC100 32M]
flashing with USPL
phone's SPL: stock SPL-1.54.0000
radio: 1.12.25.16D3 - don't see a reason to update
protocoll: 52.60.25.33U
carrier: O2 GERMAN
what have been done so far?
I've tested the pairing of my device in various cars
tested with my Renault Megane 3 integrated car kit (arkamys audio / parrot)
tested with a 2010 Toyota Prius car kit
tested with a subaru 2010 car kit
tested with Blaupunkt Toronto 400 BT head unit by phitsc
I've tried programs, suggested by the xda community
installed Bluetooth_SAP_Profile.CAB
installed BT_SAP.cab
installed Gooru_Sense_BT_A2DP_Fix_Cab_by_JVH3.CAB
installed HeadsetFix.cab
installed JetBTHFExt_1.40.CAB
reg-tweaks on "HKLM\Software\Microsoft\Obex\ObexServiceMask"
roms tried
Miri_WM65_21891_Premium_Manila_2.5_V20.0_NoHtcMessaging.rar
Miri_WM65_21893_Premium_Manila_2.5_REV22.0.rar
Energy.BLACKSTONE.23563.Sense2.5.Cookie.HomeTab.Apr.23.7z
Energy.BLACKSTONE.23566.Sense2.5.Cookie.HomeTab.May.01.7z
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.16.7z
Energy.BLACKSTONE.21903.Sense2.5.Cookie.May.16.7z
HD_Miri_6.5.X_23541_SENSE25.rar
Miri_WM65_21893_V38.0_Premium.rar
Energy.BLACKSTONE.23569.Sense2.5.Cookie.May.22.7z
(green indicates a working rom)
dear community...
please use this thread wisely for recommendations or suggestions on this topic. keep this thread a productive discussion. if you have a contact to NRGZ, feel free to report this thread, cause my afford to reach him fails.
So I hope we can figure out, why it does'nt work as it should to...
kindly regards, FS
Click to expand...
Click to collapse
Mine works fine without any cab fix.. your pda must search 4 a car kit as a bleutotth headset! comm manager /bluetooth/ set up BT headset turn your cars BT on and there you go!! i tell yo the energy roms work fine 4 me
+ 1 here
Don-Maco said:
Mine works fine without any cab fix.. your pda must search 4 a car kit as a bleutotth headset! comm manager /bluetooth/ set up BT headset turn your cars BT on and there you go!! i tell yo the energy roms work fine 4 me
Click to expand...
Click to collapse
sorry dude, not much help but i have the same experience; all energy roms (and i do mean all of them) work perfectly with my parot CK3100 but then i do task 29 before every flash & hard reset a few times after initial setup.
in addition, i also flash the latest stock rom from htc every so often.
i know this seems a bit ott but i rarely seem to suffer the buggy issues that many others do.
hope you get it sorted
It is not about Task 29.
I had problems with access through the original multi-functional touch panel in the Ford Mondeo. When I went to CLEAN ROM, all troubles are gone. The problem is that you must agree with access on the phone. This question is not on Energy ROMs displayed. I can pair phone but can not be used for handsfree calling.
Now I have a CLEAN ROM and everything is bugfree.
To be honest, no ROM to date consistently works with the in-car bluetooth kit in our Zafira. It works flawlessly with my old phone (K800i) and my wife's phone (W950i) but it's just not stable for the HD.
If it works, it'll drop the bluetooth connection after about 15mins. It's as if there is a time-out, but I've hunted the registry and both HD Tweak and Adv. Config for anything related to this but with no joy.
My current ROM seems to be about the best so far (kwbr's WM6.5 and Manila 2.1) but it still drops the connection randomly yet other times it may keep the connection for over an hour no problems.
Seems very very strange to me, but from what I've read, it's a common issue with the bluetooth kits in GM's euro cars (Vauxhall, Saab, Chevrolet etc.)
|WWE|BLACKSTONE|¯`·.¸¸.- Energy -.¸¸.·´¯ |BlueTooth CarKit ISSUE|`·.¸¸.·´¯`·.¸¸.·´¯)
@DaRulah
what kind of rilphone / radio rom do you use - pointing my research in this direction, may that's the reason... does bluetooth depends on the used radio rom?
@raistlin74 / @Don-Maco
tried all ways possible
car to phone
htc comm mgr to car
windows BT settings to car
@superseagull
having the latest carrier rom flashed before (comes with SPL 1.54 to enable flashing of 6.5+ roms)
what kind of rilphone / radio rom do you use? [EDIT: saw it in your signature ]
@malson
well, sounds logic ... the pairing won't succeed cause the phone's dialog to allow access doesn't appear. will try it with energy's titanium rom. never the less, the outdated MIRI roms /w sense 2.5 and windows mobile 6.5 works for me
@jonifen
as mentioned, the phone is compatible with my car - in basic. simply doesn't work with energy roms.
therefore I tried it with various other systems to exclude a mismatch with my car kit
well, thanks for you participation so far - may we get the clue with my problem
regards - FS
2 options?
Why only two options yes and yes? Why not a no option in the poll? I don't have a problem with nrg roms.
firespawn said:
@DaRulah
what kind of rilphone / radio rom do you use - pointing my research in this direction, may that's the reason... does bluetooth depends on the used radio rom?
Click to expand...
Click to collapse
Radio: 1.14.25.35 with the matching rilphone
Rom: Energy.RAPHAEL.23569.Sense2.5.GTX.Themed.May.13
i don't think it's a radio problem since i used that one with older energy roms, and had no problems with my car kit.
no problems here
I tried my phone with a bluetooth carkit in a BMW X5 and found no problems with it. I use latest NRG rom 21905 with CHT and latest Radio (1.17) with Rilphone 1.15. i suggest u upgrade to those as well.
GL
As this is about a genaral pairing problem I don't know if it will help u as u seem to be able to pair but just have Handsfree problems...
But as u didn't mention how u tested out the fixes I will post this here.
Remember i had a problem once when trying to pair my HD.
Base:
- Touch HD with some newer Sense 2.5
- A2DP wasn't working or Windows Mediaplayer hooked A2DP keys
AFTER I tried to fix A2DP problem (installed some "fix" cabs u mentioned above) I wasn't able to pair anymore.
Here is what i figured out:
- To get it working again it didn't help to over-install another fix - don't know why but seems that some fixes do reg changes wich break other ones.
- I had to hard reset the device
- so never try to install 1 fix after another to figure it out
- always do 1 hardreset + 1 fix then hardreset again
- only really good working fix for me was HeadsetFix.cab I posted in NRG thread - many other fixes broke my pairing capability
Now im on:
- actual NRG 2. June MaxSense 23xxx
- HeadsetFix.cab installed (otherwise Windows Mediaplayer pops up or it doesn't work for me)
- haven't had problem with pairing since several month with any NRG Rom (before it wasn't depending on NRG but on Sense 2.5 / but just had A2DP issue - pairing issue just with wrong fixes installed)
Radios I tested were .12 and .14
Tested BT Headsets/Caraudios:
- Motorola HT820
- some Sony MEX BT xxxx Caraudio
BTW for all who are interested in - i always install "AutoA2DP" or "AutoActiveSync" cause A2DP doesn't pair automaticaly in my car - just the Handsfree pairs by default.
Mimic NRG style ROM Thread !!!!!!!!!!!!
eddyve said:
Why only two options yes and yes? Why not a no option in the poll? I don't have a problem with nrg roms.
Click to expand...
Click to collapse
Yes + 1
Why only YES and YES option ...
No problems with any BT. Myy HD conects on any BT device that i have with no problems...
*****************************************************
PS: its not nice to use for your thread title the same format and characters that NRG use for all of his roms !!!!!!!!!!!!
Its a bit confusing for regular users and misleading....
And if i was you i will change the title not to mimic NRG ROM threads !!!!!!!!!!!!!!!!!!!!!!!!!!!!
colossus
|WWE|BLACKSTONE|¯`·.¸¸.- Energy -.¸¸.·´¯ |BlueTooth CarKit ISSUE|`·.¸¸.·´¯`·.¸¸.·´¯)
@eddyve
it is a yes poll (or call it simply a counter), because I want to know how many people have a problem like me
@DaRulah
well, good to know
@TheOne741
updating my radio rom asap, just to confirm that the radio version is not the source of my problem ... I will report on this
@FrEcP
thank you very much for your detailed explaination! I also do hard resets between the fixes. I will try HeadsetFix.cab in combination with AutoA2DP on a clean rom
@colossus_r
do you have anything useful to contribute? stay on topic please!
Well, thank you all so far, I will report my progress when the mentioned tips have finished... regards - FS
mimic NRG ROM thread
firespawn said:
@colossus_r do you have anything useful to contribute? stay on topic please!
Click to expand...
Click to collapse
@firespawn: Whats the matter with you? colossus_r is on the right way. Why only "Yes or Yes" in poll. And whats about mimic NRG ROM threads?
Please choose your own style for this thread.
On topic: No problem with Siemens HKW 720 Bluetooth Car Kit at all. Im using Handsfree-Profile and rSAP-Profile.
Issues with bluetooth ...
aleskow said:
@firespawn: Whats the matter with you? colossus_r is on the right way. Why only "Yes or Yes" in poll. And whats about mimic NRG ROM threads?
Please choose your own style for this thread.
On topic: No problem with Siemens HKW 720 Bluetooth Car Kit at all. Im using Handsfree-Profile and rSAP-Profile.
Click to expand...
Click to collapse
Again, it is used as a counter aaand again: stay on topic and stop cryin' like a baby about the choosen subject! I couldn't change it anymore!!!
Please do not post things like: Oh boy, mine is working fine *smiley*, cause this is worth nothing!
Sorry, I'm a bit frustrated, because a productive research on this problem seems to be impossible...
superseagull said:
sorry dude, not much help but i have the same experience; all energy roms (and i do mean all of them) work perfectly with my parot CK3100 but then i do task 29 before every flash & hard reset a few times after initial setup.
in addition, i also flash the latest stock rom from htc every so often.
i know this seems a bit ott but i rarely seem to suffer the buggy issues that many others do.
hope you get it sorted
Click to expand...
Click to collapse
Right is right i also never had bugs since energy roms march 2010
and the opera 10 never gave issues! so some flashers are doing somthing wrong! when using titanium the rom is superbly fast i also spice things up with the htc-performance.cab.
firespawn said:
Again, it is used as a counter aaand again: stay on topic and stop cryin' like a baby about the choosen subject! I couldn't change it anymore!!!
Please do not post things like: Oh boy, mine is working fine *smiley*, cause this is worth nothing!
Sorry, I'm a bit frustrated, because a productive research on this problem seems to be impossible...
Click to expand...
Click to collapse
We cant do any research if we dont have the problem
i think you should swich the the car bluetooth on and keep it pressed till the device finds it! thats what i did on other cars
or you will have to reset the cars bluetooth as shown in the manual
firespawn said:
@eddyve
it is a yes poll (or call it simply a counter), because I want to know how many people have a problem like me
@DaRulah
well, good to know
@TheOne741
updating my radio rom asap, just to confirm that the radio version is not the source of my problem ... I will report on this
@FrEcP
thank you very much for your detailed explaination! I also do hard resets between the fixes. I will try HeadsetFix.cab in combination with AutoA2DP on a clean rom
@colossus_r
do you have anything useful to contribute? stay on topic please!
Well, thank you all so far, I will report my progress when the mentioned tips have finished... regards - FS
Click to expand...
Click to collapse
set up you bT via comm.manager. dont turn Bt on just choose set up bluetooth hdset device etc/ turn you cars bt on an make shure it is visible etc by keeping the on button pressed in while searching with your gsm and thats it i think thats how it worked 4 me and will work 4 every one too!!!
study your old rom be4 you use a new one and you will know how to recognize the differenzesss amen
I've experienced something similar with my volvo. In my case it paired sometimes and usually in a call it disconnected. This happened with all kind of roms. It all disappeared after a radio update.
Somebody mentioned 1.17... with rillphone 1.15... works like a charm!
Hope it helps
(else you can try to let a mechanic update the bluetooth software in your car)
I'm tryin to use my phone in my car using the build-in handsfree device (BMW 3-series). Sometimes it works but most times the car looses the pairing after a few minutes. After that the connection is only possible when I switch bt off and on again. But then again a pairing is not possible. I already used the phone with Android successfully in the car but only once or twice.
I used several sense-builds with a variety of different kernels such as mdjs and hastarin. I also changed the connection value in the bluetooth main.conf from 7 to 15 but without any success.
What can cause a problem like this where a connection is possible only for minutes but is working sometimes like expected?
Has anyone a similar problem with a Bluetooth headset?
Thanks for your help.
======================== SOLUTION ========================
Finally I found out, that it has nothing to do with radio ROMS, nothing with the WiMo-ROM nor with the Android itself. The failure lies in the sync between android and Outlook. One of my contacts included more then 80 telephonenumbers (3 particular numbers many times) what crashed the pairing between my car and the phone. I just deleted the contact and re-added it manually. Further I stopped the sync with Outlook and now only sync appointments of the calendar...
======================== SOLUTION ========================
Sent from my HTC HD2 using XDA App
Really no help for me...
I've got the Fiat Blue & Me system in by Abarth, it has similar problems to the one you're having in the BM, if I'm right in thinking that the Bluetooth stack is part of the radio ROM then trying a few different radio versions should help. I've found one that's fairly stable but still unpairs itself occationally. it's Leo_RADIO_2.15.50.14 running on mdee jay Evo Sense Evolution with hastarin's 8.1 kernel.
Updating the radio ROM didn't help. I could make one single call but after that it began losing pairing again. That's so sad because everything else is working pretty good so far.
Sent from my HTC HD2 using XDA App
I own a BMW 320d E90 and i have no problem with BT pairing.
I use the Androide 1.5 build done by Crazy_Cbr in htcmania.com (a spanish forum), with Radio 2.15 and Official Kernel #127.
Maybe your BT device needs a firmware update if your Serie 3 model is old. I have heard that you can update it in your BMW dealer, but not sure as far as i haven't needed to do it.
Greetings! (and sorry for my english)
Thank you... I have a 2010th E92 so I think the firmware is no problem. Furthermore the Version 1.5 is pretty old. I had this one with my G1 phone and was not very pleased. I also need Sense which is - afaik - not available for 1.5. Why do you not use a 2.x version?
Sent from my HTC HD2 using XDA App
This build is based in 2.2 but his name is "Androide 1.5", the point is that is a Senseless one...
Anyway i guess the problem is not in the build. Does BT work fine with WM?
Yes it worked pretty well with WM what brings me to the point isolating the problem on the hacked Android builds. Perhaps it'll work in the future.
@Nandeh: Which ROM Version do you use for your HD2 device (Radio ROM, WM-ROM and HSPL)???
Sent from my HTC HD2 using XDA App
I found out that the bluetooth pairing is stable as long as I don't have any phone numbers saved in my phone. Any ideas?
Any updates on this?
I have a 2005 1-series. First I was running WM 6.5 on my HD2 and never had problems connecting to the handsfree built in to the car. Then I installed tytungs NexusHD 2.9 NAND ROM (Android 2.3.5). After this, I can pair with the car, but the connection keeps dropping out and then reconnecting with some random intervals between maybe 3 seconds and half a minute.
I have tried to edit audio.conf and audio_pairing.conf, and also an earlier version of audio.so with no luck.
I really don't want to get a different ROM, as I really like the one from tytung.
(Link to tytungs ROM: http://forum.xda-developers.com/showthread.php?p=16555125#post16555125)