Related
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
BombaMyte said:
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
Click to expand...
Click to collapse
I am currently using my Jawbone with Schnaps 4.01 Lite rom and no problem. Before that I have been using all of Matt's Pandora Kitchen roms, right up to the latest and never had a problem. I ran Schnaps 4.30 Full rom too, but really can't remember if I used the Jawbone during the testing time. If someone else can't help I can flash that rom again and test the Jawbone with it too. Let me know ho wit goes.
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
I have an 8525 running Schaps 4.30 with radio 1.48.00 and mine is working. I did however have to return one Jawbone because it would connect and I could hear the conversation but the mic didn't pick up my voice. I tried that one on my wife's razor and it had the same symptoms though. What radio are you running?
Using with TNT's latest ROM and no problems, however not real impressed with Jawbone so far. Most people I call say it sounds "tinny".
mthomas said:
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
Click to expand...
Click to collapse
AFAIK, the BT radio works. Like I said, I can pair up with it just fine, and even see the other BT-enabled phones/devices at my job. I just can't get any type of audio from my JB. I'm currently using vp3G as well.
UPDATE: Well to be on the safe side, I tested my Jawbone on a couple other phones; sure enough it's working fine, so it's got to be something up with my poor Hermes... Any advice?
Mine Jawbone Works fine also. I remember when I first got it I was having trouble with my sound. I remember changing the audio bitrate from 48 bit to 44 bit in the advanced config utility 1.1 Also try changing the stereo setting to mono.
May help you out, hope so.
Just a quick update: I reflashed vp3G's 3.62 ROM, reset my JB and repaired it; same effect, nothing. Just to be on the safe side I paired the JB with my Wizard, BB Pearl, and a couple of phones at my store and it works as it should.
@ mthomas: I'm using 1.48.00 for my radio. Since you and I seem to have the same type of setup, did you install any other cabs that help your BT out?
Do you have another Bluetooth headset to test. Even thought it can pair ok, it only means the "data" channel is working. The problem could easily be the voice channel which is not working. If possible, may be borrow another headset to try.
That's my next idea. I think I have an old Plantronics I can charge up and test out...
*BUMP!*
Gotta keep this fresh. Funny thing I noticed though: when I have the Jawbone connected and the phone rings, I still hear it's little tone in my ear, but no audio comes or goes through. No registry edits have been made; I've even done a hard reset, re-paired and tried again, to no avail.
C'mon you guys! Why am I the only 8525/Jawbone user around here that *can't* use his Jawbone??? Help me out here...
wish i had the answer. im using the most current att radio 1.54.07.00. how did your device work w/ another headset?no additional tweaks
Okay, now I'm getting pissed.
I tried using my old Plantronics 320. It pairs fine with the Hermes, but making phone calls is a no-go.
The only thing I removed (from anyone using vp3G's 3.62 Full) was Sleuth's PTT Fix; I need PTT more than being able to re-map the button. So I doubt this is the culprit.
WTH can't I use my good Jawbone with this thing?!?!
Quick *bump*
Same Problem
I have tried everything, I can hear the calls just fine but no sound from my mic. I have paired with other phones & it works fine. Please let me know if you find a fix!!
UPDATE: I tried using a Moto H700 and a Plantronics 340-no dice. Now I'm starting to think if it's a BT stack issue...
Now I'm completely stumped. I just flashed back to the original ATT WM5 rom, paired up, SR, then made a phone call to my 8525 from my house line. Jawbone rang in my ear, sure. I answer the call, no sound.
Could there be a problem with my BT radio? And if there is, how can I be sure/troubleshoot it?
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
myv6mustang said:
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
Click to expand...
Click to collapse
Good thought... But I already did that, still no joy. In fact, I just flashed over to HTC's official TyTN rom, and still nothing. I'm going to call a friend of mine and see if I can get it to work on their 8525. Here's a good ? tho: Should it matter if it's Cingular or AT&T branded? Are there any differences in hardware between the two types? Or could it be a faulty BT radio? I'm racking my brain trying to figure this out.
Worse comes to worse, I'm sure I could exchange my Jawbone; I *do* work for AT&T so it should be okay...
Okay, here's another question: If I were to flash *ALL* the way down to the original Cingular shipped ROM, RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship, would this have any effect on the BT stack? I'm only asking because I can't seem to find any type of information about replacing the built-in stack (outside of the Widcomm project and that's too beta for me ATM), and I still can't understand why so many headsets that I've tried with this damned 8525 don't seem to work, but so many people here @ XDA can use theirs. There's no differences between the Cingular branded and AT&T branded models (at least hardware/software-wise), and if I pair up my trusty Jawbone with another 8525 (AT&T branded, btw), it works fine.
I know I've been going back and forth with this, but I did pay a good amount for my 8525 and I don't want it to be partially or mostly functional. Hell, if my poor Wizard can handle my Jawbone, why can't my Hermes?
BTW, thanks for all of the suggestions you guys have given me to help me with this problem. Even though none of them have worked, I still need to give props where they're due.
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
BrianP6 said:
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
Click to expand...
Click to collapse
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
BrianP6 said:
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
Click to expand...
Click to collapse
This bug appears only when 2 or more devices get paired.
I've been trying everything, even abusalza himself suggested some module replacement. i'm working on replacing drivers and certain folders in sys in my kitchen but still nothing yet... so far not yet, but it's fixable, i just gotta figure it out.
Thanks Josh,
I guess you'd know this anyway, but for completeness and for the benefit of the whole forum.........
Even though the paired devices are no longer shown in the Bluetooth Devices window, and you can no-longer use your HTC to pair more devices, then so long as you carefully initiate the pairing from the other device, it will be recognised, PINs will be requested and devices configured appropriately. I have just done:
Audi A4 in car kit
Laptop via Internet sharing
Jabra earpiece
None appear on the Devices window, but all (so far) appear to work perfectly.
Cheers,
Brian.
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
austinsmartie said:
Has this happened to anyone else?
Click to expand...
Click to collapse
Yep, I have experienced everything you mentioned at one time or another, even the square characters showing up in the device list.
I have gone all the way back to test Faria R32 ROM. It's amongst the best I've found for A2DP with the S9's along with some of PDACorners early ROM's. The drawback are that it doesn't have the 1% battery increase .dll cooked in and also still exhibits the "numbers for character during a call" bug.
It does have nearly 31 MB of memory free after fresh install though. (using 4MB pagepool - default is 6MB)
austinsmartie said:
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
Click to expand...
Click to collapse
It frustrated me enough that I started building my own rom!
I released one version here that I have been running for quite some time with no issues in the bluetooth at all.
I need to tweak it a bit more to make it "polished" but it is very useable and stable. I just wanted to run it for a while to see how it is going to act over a longer duration before I continue to fool with it, and I have been rather busy here lately.
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
joshkoss said:
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Click to expand...
Click to collapse
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Hmmm - doesn't happen on my ROMs...
The suspect things I'd be looking at in SYS are:
Bluetooth
Bth_A2DP
Bth_HID
Try replacing those folders with known good ones and see if the problem still happens...
austinsmartie said:
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
Click to expand...
Click to collapse
No Magic potion! lol
I basically did what CRCinAU described. (His rom doesn't have the issue, and feels a bit faster than mine. But, I was looking to create "My perfect rom").
But I also replaced files in the redist folder with "bt" in their name, with files from a known working rom (anryl's 20755). Like I said I wanted to run the rom for a while, now I just need to go back and tweak and clean up some things in the rom before I make another release.
summary
stickybud said:
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Click to expand...
Click to collapse
it is a really odd issue and seems to only affect the hermes... Here is the deal, Some chefs when porting sys grab the cplmain.dll to get the build number and keep some other items in their kitchen sys for stability purposes... I have noticed in my experience when porting, if the cplmain.dll does not match some other components with the same build number it will cause this issue. usually resist, shell, os, folders have been containing these sensitive items. so in short, if the issue is occuring cplmain.dll in redist folder does not match other components in your sys causign the conflict.
edit, and oh. i've tried replacing all bluetooth which had no effect.
So to fix this, the chef needs to report sys correctly and recook the rom.
Hello everyone,
I'm having a problem with the RCD 510 Premium Bluetooth kit that is installed on the new VW Scirocco and its been troubling me for over 2 months now.
When I first got my Scirocco the Bluetooth connection was working fine (for 3-4 months). One day out of a sudden the Touch Pro II was not pairing anymore with the car's bluetooth kit.
At the time I was using Windows Mobile 6.1 that originally came along with the phone. I tried the basics - deleting the connection, re-pairing - with no success.
So I gave a shot at phone's factory reset - still no luck. The phone is recognized when I use the "Device Search" function on the car, it prompts me to enter the pass code provided, I do so, the phone loses the GSM signal (which of course is normal) but then suddenly I get a message on the RCD510's main screen "No bluetooth connection to phone" that lasts for about 2 seconds.
Since the problem began, I tried factory reset the phone (as I mentioned before), and tried pairing before installing even a single software, still no luck.
I tried multiple ROM's in the meanwhile (I mean third-party ROMs from this forum) and now I am using the official Windows Mobile 6.5 from HTC for my phone.
I also did many tests using third-party applications for the rSAP protocol (JetWare hands-free extension, SAPSettings, some patches and drivers found around the net here and there) even though there is native support for rSAP since the first firmware that came along with the device.
As I mentioned before, the phone was pairing fine the first 3-4 months.
Please note that this phone uses the Widcomm Bluetooth Stack - not the Microsoft one.
Any help/ideas would be greatly appreciated.
PS: I apologize for the big length of the post, but I believe the more the information I provide, the more the chances to get proper help
Sorry i cant help you but.. I want your CAR...
Any pics?
Well.. try this
Unhook the cars battery. Let it reset the radio (make sure you have the radio code if any) and try again.. maybe the radio is holding some sort of setting. Resetting to default (like with the device) might do the trick..
.
Thanks for the idea. I'm kind of worried though plugging out the battery, because there are many settings besides the radio that probably will be lost if I do so.
You know all these new cars and their complicated electronic sensors...I don't mind losing minor settings for the car that I have adjusted, my main concern is that if anything goes wrong, I will probably have issues with the car's warranty. I still have 2 and a half years of warranty.
I' will probably have a talk with the dealership before doing that.
Many thanks for your thought though
hi i like to know if pairing went okay with the 6.1 rom because if so maybe when you switch back to this rom problems are solved
Nop
Unfortunately no
It was one of the first things I tried. Switching back to the official 6.1 ROM. I actually kept it saved on my hard disk and I tried it a couple of times - I mean when I tried other ROMs from time to time - hoping it would resolve the issue.
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
First logical thought would be that something has changed in the car's settings. But I have an Athena X7500 that pairs fine with the car up to this day. My car's dealership isn't much of a help...
Second thought - phone settings mess-up. But as stated in my original post, no factory reset helped, no switching to other ROMs, no playing around with settings.....
I'm really desperate. I'm thinking to switch to another phone, but besides this problem I'm quite satisfied with the TP2. And I do "need" Windows Mobile based phones, because I sync with Thunderbird's Lightning via BirdieSync for a long time now, and I am not willing to revert back to the horror days of MS Outlook. I carry my TB profile for over 2 years now and its customized the way it suits me for manipulating my 10+ email accounts.
Thank you very much for your reply though
Any other thoughts/recommendations?
i downloaded firmware 1.20 from volkswagen hope this will help me will try tomorrow with my laptop i am with a touch adapter connected to rns 510 no pairing with tp 2 at the moment for me the only workable solution is a duo sim with my old blackberry bold meanwhile i love he TP2 so hope i can get it to pair with my premium touch adapter volkswagen carkit any other suggestion or solutions are very welcome cheers
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
what radio where you on first couple of months
Nice thought about the radio....but unfortunately I don't remember.
Currently I am using v4.49.25.17 that was upgraded with the latest official HTC firmware of WinMo 6.5 if I am not mistaken.
I am 90% positive though that the problem started before even upgrading, back when I was using the first release of WinMo 6.1 and the unknown version of radio, and everything was working ok at the beginning.
I know, I am not helpful at all but frankly, this problem surprises me as much as you.
You mentioned a firmware upgrade - for the RNS right? Not the RCD....
Do you by any chance happen to know if there is a firmware upgrade for the RCD510 and where can I get it from?
Thanks for your help.
looking-g:
I just realized that you are having a problem with the RNS.
Did you had this all along? I mean, did you ever managed to get it working and then it stopped, or you never had it paired?
I am just asking to see if I can be of any help...
well the problem is not with the rns 510 but with the touch adapter which come delivered as premium carkit i use to pair everything with it blackberry,s nokia,s and also a touch dual (niki) without any problem but now with my new phone the tp2 its not pairing it also never did after i fill in the pincode it gives an error message it should connect with the touch adapter my car by the way is a golf gti mk6 cheers, mark
You kind of lost me there.
What do you mean "touch adapter"? Is this a component of the RNS 510? Because I have never heard of it...
Have you determined a solution?
I just picked up a new VW Jetta with premium bluetooth and it worked the first time and not since.....
You guys are scaring me -- I have an Audi A3 TDI scheduled for delivery in January, and it'd be a bummer if its Bluetooth didn't work. FWIW, my current car has a Sony MEX-BT3700U headunit and the Tilt 2 pairs with it in both handsfree & A2DP modes.
3waygeek: You will be probably fine. I think Audi does not have anything to do with Nokia regarding building their units.
Wish you best luck with that.
Extra info
Some more information regarding the whole subject:
I found out that when I press the "Emergency Call" option on the touch screen of the RCD510 (i.e. try to call the international emergency number - 112) and then immediately end that emergency call, the next time I try to pair the Touch Pro 2, it does pair!!! But it has no signal at all, and if you try to make a call you get a "Dial up error" (or something like that, can't remember exactly)!
Any ideas what could be the reason for that?
Thanks.
Your problem is common to VW/Audi's. Chances are the car kits have the rSAP Bluetooth unit. I had exactly the same issue in my A6 using rSAP, as soon as i upgraded to wm 6.5 the problem went away.
Yes, indeed the car kit uses the rSAP profile, as well as the Phonebook Access Protocol (PBAP), but both of these protocols are supported by the TP2. Actually the rSAP functionality I believe is support in Windows Mobile 6.1 and above - I mean besides the fact that your phone's BT radio must support it in order to work correctly. (Without being entirely sure for the above comment).
And some more info for those who are willing to give an opinion:
I did eventually decided to remove the car's battery. I left the car without battery for approximately 40 minutes. Now here's the strange part: All the settings of the card indeed reset (window settings, light settings, etc) BUT the RCD510 was not affected at all by the battery removal! Yes, as weird as it might sound, the station list was there, bass/tremble customizations were there also, everything in place (regarding the radio unit always).
Side note for all those who might remove the battery from a similar VW car:
As soon as I plugged the battery back on, I had somewhere 15+ warning indicators on my dashboard turned on. From ABS malfunctions, air pressure, EPS malfunctions etc. But after rolling the car for 3m or so everything turned off. Back to normal. Probably had something to do with the electronic sensors giving proper signal to the car's "brain". Just my opinion.
Now, besides that - the fact that removing the battery didn't perform a reset of the radio (RCD510) unit, I also tried reverting my Touch Pro II to a WM 6.1 cooked ROM - don't remember which one exactly - but that didn't helped either. Same stupid error message after pairing for 2 secs: "No bluetooth connection to mobile phone".
And to confirm again: My X7500 (Athena) with a cooked WM6.1 ROM from michy still pairs and works fine. (Tested it last night, just to make sure that battery removal didn't had any side-effects)
PLEASE help me if you can. Any suggestion/recommendation will be greatly appreciated.
PS: I decided to contact the car's dealership to inform them about the whole problem. I will post soon regarding how that went...
Thanks for your time everyone...
By the way, does anyone knows the proper way to reset the RCD 510 to it's factory default settings? Besides the function that is given inside the menu itself - I already tried that. I was just wondering if there was a "hidden" way that will entirely wipe all settings/customizations from the unit....
Hi guys! I m in the same situation: Sirocco + TP2 with 6.5 from Orange. Any progress from your side? Ideas would be greatly appreciated!! Cheers, P
Unfortunately!
No friend, sorry. No news yet.
I do keep the post open hoping that someone will give me a new year's present
It's nice to know that I am not alone though
Hello. I wasn't sure where the best place to post this so I am starting here.
I have a Touch Pro 2 and absolutely love it. I flash the phone every time a new ROM is released from the Chef I like and have been able to overcome most obstacles but I have one that is sticking me.
I bought a TomTom One XL and one of the biggest selling points for me was that it can update traffic using the Blu-Tooth of your phone and do all sorts of nifty stuff including rerouting you around accidents and such. It is a paid service and I am paid up through next year. It worked fine even with my old Motorola Razr and it has worked ONCE with my TP2. The phone pairs with no issues. Then there is a setup to go through where it asks among other things the phone model. The Touch Pro is on there but not the Touch Pro 2. There are also several other HTC phones on the list as well. It will then try to guess the correct settings to communicate with wherever the traffic info comes from.
What really gets me is that I don't see how this is phone dependent. If it is blu tooth and it pairs, what is the hangup? I use T Mobile and there are options of what connection to use like "TMobile 1" 2 3 4 ect. I have tried every possible combination. TomTom support won't help because the phone isn't on the list. Tmobile Tier 3 are actually pretty knowledgable but haven't been able to help so far. Any suggestions? I am happy to provide screenshots or any other info for anyone that might be able to help. Thanks!
Hi
I dont know cause I dont use this but...
Did you try to use a different phone selection in setup rather than the TP because I think the TP2 has a different bluetooth stack so its quite different from the TP.
I use a software called Salling Clicker and to make it work I have to use a generic WM5 (Broadcom) selection in the setup.
Try to find a Phone (with the right resolution? probably not an issue for this software.) that uses the broadcom bluetooth stack. And see how that goes.
Good luck.
Hello,
I know that this would be better posted to one of the development forums but (new member) can't post there...
anyway, I have the captivate glide and I recently installed literom from the greater good. Anyway, I'm running into some bluetooth issues and I was wondering if anyone has had any similiar issues? The forum for that rom does not mention the issues that I'm having (at least not that I found).
Basically, my bluetooth works fine. As long as I don't reboot my phone. Any time I reboot, my pairing information is lost for any devices I had. I can scan for devices, but when I try and connect, it says invalid pin or connection refused. If I run through the pairing procedure again, it works until the next reboot.
Anyone have any ideas for me? I like this rom and don't want to re-image it with something else... my bluetooth worked fine on the last rom I had installed (but nothing else did pretty much, which is why I reimaged it)...
sorry for throwing this out in the general forum, but to be honest I'm not 100% sure that my issues are related to this ROM just mostly sure... anyway, any help would be greatly appreciated.