The point of this thread is that 1.64.08.21 is compatible for some and incompatible for others; hence what I'm trying to express here is that the bug/issues caused are due to the Radio and NOT the ROM itself.
Since quite sometime I've been testing miscellaneous ROM's over various Radio versions. Also have been closely monitoring every single BUG pointed out in bepe and other chef's thread. The same bug issue has been also brought up in ASerg ROM. I personally feel his ROM is bug free as I haven't come across any issues.
My speculation has narrowed down towards one common problem giver i.e. the Radio v1.64.08.21 which is now used by 90% of the Polaris users.
I strongly feel that v1.64.08.21 is incompatible with the latest ROM version 19209 & Protocol 25.69.30.05 and even the earlier ROM versions i.e. 1920x.
To be sure of my study I've tested ALL possible ROM's in this forum using the factory radio 1.54.25.14 and till date haven't faced a single bug issue which has been repeatedly brought up by misc members on this forum.
To clear this problem, request some of you to help me test some things out:
- Can I request you to re-flash your radio to 1.54.25.14 and then test the same ROM for the bug's you have been facing
- All NEW Polaris owners, please DO NOT flash your Radio rather just the ROM.
- Existing Polaris owners on a non-1.64.08.21 radio, please test whether the bugs exist on your ROM's.
After all 1.6.4.08.21 is a Radio extracted originally from a Russian Kaiser ROM, it doesn't make it 100% compatible as the factory Radio for Polaris.
Strongly looking for some views and feedback from everyone
What are your noted bugs?
what the actual bug is?
@taiseer999:
I'ven't faced the same issues which other members on the forum have been mentioning, even using the same ROM which they are on as well.
@windirt:
I personaly feel that using a Kaiser Radio on a Polaris is "possibly" causing the BT to remain on and other miscellanous issues that have been brought up.
I'm using a self-cooked taiwan cht rom (wm6 18129) with radio 1.64.08.21. works very well for one more week, never encouter the BT issue as you described.
windirt said:
I'm using a self-cooked taiwan cht rom (wm6 18129) with radio 1.64.08.21. works very well for one more week, never encouter the BT issue as you described.
Click to expand...
Click to collapse
I also never faced any problems with Bepe 0.67 WWE release and 1.64.08.21. I can turn my bluetooth on or off, the blue light isn't flashing if my bluetooth is off, and I never had any problems connecting to a device or what so ever. Maybe there are revisions of the hardware...
I have been using 1.64.08.21 from
http://forum.xda-developers.com/showpost.php?p=2051354&postcount=1
and no problems with Bebe's ROM. WiFi, Bluetooth, and 3G work fine, only problem I am having is using Windows Live with 3G, which cant connect all the time. But this also happened with the original radio and ROM.
PB of BT
Hi,
very intersting post Jibreil. I think your right when you recomand not to change the original radio of polaris. Since I change my radio, I definitively loose my BT and my FM Radio. Both was working before I make the "update". now I have to send my polaris back to the seller and its a very very disturbing situation
So I confirm: do not change your radio if you want to be sure of kipping your BT. Another thing about that: maybe Im wrong but I think that the battery drain is much better with the last radio (1.64....) it's a shame !
nooms
067 bepe
nooms said:
Hi,
very intersting post Jibreil. I think your right when you recomand not to change the original radio of polaris. Since I change my radio, I definitively loose my BT and my FM Radio. Both was working before I make the "update". now I have to send my polaris back to the seller and its a very very disturbing situation
So I confirm: do not change your radio if you want to be sure of kipping your BT. Another thing about that: maybe Im wrong but I think that the battery drain is much better with the last radio (1.64....) it's a shame !
nooms
067 bepe
Click to expand...
Click to collapse
After flashing I noticed a drastic loss in my signal, may be it doesn't work well in this part of the world. I have replaced three phones, imagine how frustrating it must be for me
The point of this thread is that 1.64.08.21 is compatible for some and incompatible for others; hence what I'm trying to express here is that the bug/issues caused are due to the Radio and NOT the ROM itself.
Related
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
Hi all,
it is well known that most of HTC's devices do not support 2 sides call recording. Hermes is obviously one of them. I've noticed that the problem has been worked out for the Kaiser here. Is it also possible for Hermes?
come on guys, just can't believe no one is interested in calls recording on Hermes!
more and more info spreads trough the forum here and here. i've tried to make it working on my Hermes (tested on CRC's 13.3 and Josh's V15) but without luck. is it possible that the problem lies in radio revision (mine is 1.50.00.00)? I am willing to try different radios but i'm bit hesitant after reading many ultramag69 warnings of possible brick. can anyone try mskip's cab and report results?
Parseval said:
come on guys, just can't believe no one is interested in calls recording on Hermes!
more and more info spreads trough the forum here and here. i've tried to make it working on my Hermes (tested on CRC's 13.3 and Josh's V15) but without luck. is it possible that the problem lies in radio revision (mine is 1.50.00.00)? I am willing to try different radios but i'm bit hesitant after reading many ultramag69 warnings of possible brick. can anyone try mskip's cab and report results?
Click to expand...
Click to collapse
Negative.
WM6.5 21195.9.3.21.1
Radio 1.47.00.10
thanks nebula28
just flashed radio to 1.56.70.11 with CRC's 13.3, still no luck. will try some other roms and report here.
Thanks. Seems that Hermes is more difficult.
apparently,
just tested with TAI's Golden Globe V10 (radio 1.56.70.11), still the same. i am going to try some of the stock roms.
You won't have much luck with them either and they're crammed with bloatware. I don't believe theres been much success with recording both parties in a phone call.
Parseval said:
apparently,
just tested with TAI's Golden Globe V10 (radio 1.56.70.11), still the same. i am going to try some of the stock roms.
Click to expand...
Click to collapse
A guy reported positive results with earphone. It's weird that he claimed negative without earphone.
His environment:
WM6 WWE 5.2.1620(Build 18125.0.4.2) English ROM
RADIO : 1.47.00.10
Audio Notes Touch v1.02
it worked with earphones for me once as well i had one of them in my ear and the other one was hanging loose. it turned out that it was so close to the mic that the sound was recorded perfectly
ok, so just to report back, i've tried few different roms and all failed. here is what i've tested:
- TAI's v10 with 1.54.30.10 radio
- Official Telstra 3.62.305.5 with radio 1.54.30.10
- HTC official 3.54.255.3 with 1.48.00.10 radio
- latest Orange SPV3100 WM5 (yes, 5) 2.11.61.3 with 1.38.00.01 radio
all of them with Vito 1.37.
I am going to give up. Maybe someone else will find the cause of this? Maybe you have some ideas what to try next?
Hi All,
Ever since I flashed a WM6.5 based ROM, I'm having problems with my Jawbone bluetooth earpiece .
After a while I can't use it, I believe it disconnects although the BT icon still shows connected.
I can't answer a call with it, and once I dial I can't hear anything through it.
When I turn both BT and the earpiece itself OFF and ON I get connection back.
Anybody experienced this? Does it have any relaitons to WM6.5 23XXX builds?
I've seen this happened in ROMS by NRG 23016/23071 build and Dutty R7
help please,
thanks,
R
radio 1.17?
Rami9 said:
Hi All,
Ever since I flashed a WM6.5 based ROM, I'm having problems with my Jawbone bluetooth earpiece .
After a while I can't use it, I believe it disconnects although the BT icon still shows connected.
I can't answer a call with it, and once I dial I can't hear anything through it.
When I turn both BT and the earpiece itself OFF and ON I get connection back.
Anybody experienced this? Does it have any relaitons to WM6.5 23XXX builds?
I've seen this happened in ROMS by NRG 23016/23071 build and Dutty R7
help please,
thanks,
R
Click to expand...
Click to collapse
Have you seen and read this thread. Your answer may lie within. I've also moved this thread to the general discussion forum
Rami9 said:
Hi All,
Ever since I flashed a WM6.5 based ROM, I'm having problems with my Jawbone bluetooth earpiece .
After a while I can't use it, I believe it disconnects although the BT icon still shows connected.
I can't answer a call with it, and once I dial I can't hear anything through it.
When I turn both BT and the earpiece itself OFF and ON I get connection back.
Anybody experienced this? Does it have any relaitons to WM6.5 23XXX builds?
I've seen this happened in ROMS by NRG 23016/23071 build and Dutty R7
help please,
thanks,
R
Click to expand...
Click to collapse
this is also happening to me, i'm using miri's wm 6.5 rom.
strange thing is this does not happen when connected to my car radio bluetooth, only happens with my jawbone 2.
i'm really thinking of going back to one of kwbr's stable wm 6.1 roms. they're fast, reliable, and don't have the annoying bugs that wm6.5 and htc sense still have.
Hi,
I did see this thread, but they are talking about controlling the sense with BT headphones. I downloaded the BTfix.cab but didn't try it, because thought it wouldn't help.
Will try it now and report.
Thanks,
Rami
just want to say, with the same ROM i.e. duttys R7, my jawbone works fine.
frustin said:
just want to say, with the same ROM i.e. duttys R7, my jawbone works fine.
Click to expand...
Click to collapse
What kind of manila are you using?
I just installed the BTfix like spartan recommended - now the control works but no audio in the headset....
Can it be connected to hebrew support?
Rami9 said:
What kind of manila are you using?
Click to expand...
Click to collapse
it comes with 2.5 doesnt it?
BTfix dont work for me at all.
Installed both ohone memory and storage card.
Still starting mediaplayer... when pressing start on BT-headset.
Dutty 6,5 leo 7
Can you post a link to to the latest kwbr 6.1 ROM?
thanks,
R
I'm not sure which radio version I have, but if you think a specific verison should be used for this to work, please say which.
Rami9 said:
I'm not sure which radio version I have, but if you think a specific verison should be used for this to work, please say which.
Click to expand...
Click to collapse
i'm using 1.14, not that i think it makes a difference.
Radio version is 1.09.25.14 does this mean 14 or 09 version?
It's not manila related.
I've flashed Miri's v30 version WM6.5 with manila 2.1 and it is still happening.
My card BT is working well (Parrot 3200LS), though as with all ROM versions I can't manage to sync the phone book data.
Rami
Rami9 said:
Radio version is 1.09.25.14 does this mean 14 or 09 version?
Click to expand...
Click to collapse
it's the 1.14 version.
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)
so, i remember that I changed various roms and the mic worked fine and then I remember I did a radio update and now its not working... can it be that?
i dont want to have to roll back if it isnt?
my desire hd's current radio is: 12.54.60.25U_26.09.04.11_M2
AND when it was working fine the radio was:
12.28e.60.140fU_26.04.02.17_M2
Can someone please help me, thanks..
personally i dont think it is the radio, the radio is for the wireless stuff gprs/wifi etc (afaik)
you can always be sure by rolling back as you said, but it sounds like hardware to me.
as far as i know,
every ROM has their own radio preferences...
and radio used for the signal receiver, and something like that..
but one of m friends said that, he read something somewhere, unmatch radio caused someone stayed in a loop boot condition..
so maybe you wanna look up again to the ROM that you used, and match the perfect radio for it
or you can just rollback...
Hello
Radio has nothing to do with mic
Definetely not the radio. Either ROM / Hardware / Reception.
Radio only deals with all the wireless stuff (bluetooth wifi etc.)
I think you may have got a kernel problem. Try and reflash the kernel.