Hi guys,
I am at the end of my tether... I just bought a JVC head unit with on board bluetooth, so I can use it as a car kit. But I can't get my Treo 750 to pair with it! It just locks up after I enter the passkey... and the car kit just says "error" after a certain amount of time. I'm running a vanilla (extended ROM removed) version of the 3 Australia ROM.
So, I rolled back to Windows Mobile 5... same problem... UNTIL I went into the Bluetooth settings and setup an incoming COM port. Then it paired up perfectly and all was well.
So I've reinstalled WM6, but it doesn't have the option to create an incoming COM port. That's really annoying. I've googled a heap, and searched these forums a fair bit too, but haven't been able to find any sort of workaround. Is there a registry hack, third party program, or some other way I can tell it to allow an incoming connection from the car kit?
Thanks in advance!
Has anyone had any ideas on this? I have a real issue now, as I rolled back to a WM5 ROM which I found on these forums but I'm having awful problems with it - it drops calls all the time and sometimes they just go silent..... the call stays connected but I can't hear the person on the other end.
I really need to get either the original Telstra WM5 ROM, or a way of getting WM6 to work with my car kit! Any ideas... anyone??
Okay... now I really feel like I'm talking to myself but anyway.... thought I'd give an update.
After heaps of trial and error, I managed to install the Universal version of the Broadcomm bluetooth stack onto my device. And it pairs - hooray!
However... when I make a call, no sound comes through the speakers
No other version of the Broadcomm stack will run on my Treo, I just get the memory error that lots of other people have mentioned.
Chalk another person down who's royally annoyed with Palm for putting such a dodgy implementation of Bluetooth into these devices. It's my one and only bugbear to date.
I have exactly the same problem when pairing my WM6 Treo 750 to a Parrot MK6100 carkit. After entering the passcode on the Treo, the device just hangs. The carkit says it has connected succesfully, but nothing happens. After restarting it does not recognize the carkit at all.
Did you find a solution yet? I am also looking for a different Bluetooth stack that is guaranteed to work with the Treo.
Good to see I'm not the only one. No, I haven't found a solution yet unfortunately
The closest I've come is that hacked Broadcomm Bluetooth stack. My only hope is that some nice developer will help us develop something that works!
Hi Ben,
I solved my problem yesterday. I tried two suggestions.
1) Leave the passcode field blank (do not enter '0000') and press next
2) Install http://www.jetwaremobile.nl (fully functional 30-day trial)
After that pairing succeeded in a couple of seconds and all is working well. Let me know how it works out.
Thanks very much MattMax!
I had tried the Jetware software previously, and it didn't help. But I hadn't tried leaving the passkey field blank. Did that this morning... it popped up with a connection dialog asking if I wanted to allow the connection... went back to the passkey screen, I entered 0000 and away the sucker went. How simple was that!!
I just upgraded to the latest ROW2.23 WM6 ROM the other day, so I'm not sure if that made any difference either. But it's now paired and (seems to be) working well, just need to make and receive a few calls to make sure.
Thanks very much for your suggestion!
Good to hear that it worked out!
I had exactly the same experience, leaving the field blank, after that entering '0000' and it worked. I had just installed Jetware Mobile, but apparently that is not necessary for the solution.
Related
I've recently purchased a BT-359 bluetooth GPS receiver. It looks sweet -- and it'll look even sweeter once its little blue light is blinking quickly indicating that its paired with my Treo 750.
I strongly believe the issue lies with the MS bluetooth stack, and I very much want to upgrade to the Broadcom / Widcomm stack. There are very active boards in all the other phone forums talking about porting a version of this vastly superior stack to their hardware platforms -- I'd like to make this the call for someone to do the same for the Treo 750. Better yet, I'd like to add this thread as a call to Broadcom to charge each of us $20 for something that should have been included in our phones in the first place - I'll hapily pay it.
If anyone has any ideas for getting the Braodcom / Widcomm stack working on a Treo 750 then please post it here. My entire day of internet searching has me confident that there are many Treo 750 users who will appreciate it.
I'll post my sob story below - happy hacking.
As I mentioned above (in the opening post of ths thread) I've got a vested interest in finding a way to get the Broadcom / Widcomm stack onto my Treo 750.
Alright, I've now submitted a support ticket to GlobalSat (they only do "selective" telephone support). I've also tried several other work arounds that have necessitated several hard resets of my device. I'll list a few of the solutions I've tried below, so that other frustrated users can hopefully save themselves a few steps (and headaches). Before I start this, i've got to give a plug for Sprite Backup which has made the process of trail and error bearable. I've got several work apps installed (most painfaully mNotes) which are a chore to re-configure. I'm glad that Sprite was around to restore my handheld after each of these solution attempts. Things I tried:
1. From Aximsite, I installed the Broadcom Bluetooth StackX51V05.cab -- I tried this file first because it had worked for several Dell Axim users trying to pair the same BT-359. It was also attractive to me because it provided me a path out of the MS bluetooth stack and into the Broadcom / Widcomm bluetooth stack, while also offering an uninstall option. The program installed easily, I made a couple registry tweaks suggested at Axim site, and I performed a soft reset. When the phone re-booted, i received a error informing me that I didn't have enough driver memory to load the Bluetooth Radio. I downloaded a task manager and turned off everything I could, all to no avail. Finally, I had a hunch that perhaps the Axim bluetooth was operating on a different hardware COM port, so I tried setting the registry settings for the new Broadcom driver to 0 through 9 (rebooting after each setting change) to see if that would work. In the end, nothing worked. I did get access to the broadcom interface and I can definitively say that there are far more options available in that driver than in the MS driver. I can also say that, from what I read, consensus is that the braodcom driver is far superior to the MS driver.
2. Next, from this site (XDA developers), I tried the BBS_HERMES_03.zip, and the Helmi_Hima_BroadComm_1.7.6.0500.ZIP both of which have been developped by Hemli_c who is aparently the god of this stuff. Both yielded control panels that looked similar to the Axim site solution, however neither of them worked - they both gave the same memory error. I played around with many more registry settings here trying to get them to work, again, without any luck. These were the most detailed instructions I found - I'm happy to give tips to anyone trying to better my results. http://forum.xda-developers.com/showthread.php?t=285696
3. Next, I became very interested about the WM6 "cooked roms" which are available on XDA. Now this is where I really wish the Treo folks were more geeky (or I had the time to figure it out myself). The other hardware platforms all have SEVERAL WM6 implimentations cooked up, each touting the best mix of CAB add-ons (including the broadcom bluetooth driver). I downloaded Helmi_c's, but it wouldn't work on my Treo (I did learn that to get into bootloader mode on the 750, you need to hold the side button while you press the reset button inside the SD card door). This was a bit of a nerve racking procedure, as I was convinced Sprite couldn't bail me out of that mess -- i was half thankful when the ROM refused to load (although I am excited to get WM6 loaded on my phone).
4. Finally, I sent another support request to GlobalSat in hopes that I'd get a response. I'm very excited to get this toy working, and this messing around is finally starting to get past the fun stage, to the genuinely annoying stage. I'm actually starting to think that I might not be able to get it to work (at first I just thought it'd be a challenge that would be kind of fun).
If anyone has any questions, or suggestions, I'd be glad to hear them.
I'll post again as I find out more.
I don't know that I can help any technically, but you have my moral support. The MS bluetooth stack is horrible and a constant source of headaches for me. Thanks for all of the effort and thanks for posting all of your information. Even if, in the end, you don't manage to slay the beast you have at least earned yourself a happy face sticker from me ;-)
I use the widcomm stack on my axim X51v and it is indeed superior to the ms stack.
It would be great to use it on my treo.
It is so much better and with a lot more options.
My skills about these things are close to zero, but you do have my moral support too.
First of all, an update on USGlobalSat... they aren't winning any points so far. In response to my query about their GPS receiver not pairing with my Treo 750 I got the following response:
Thank you for contacting USGlobalsat's online care. In reply, we recommend a 72 hour battery removal allowing the device to reset. In many cases, this action corrects many performance abnormalities. If problems continue, then proceed by contacting the original reseller requesting a product replacement.
Now onto some more positive news. I had some temporary success with one of Helmi's Bluetooth stacks for the Universal. The specific file I loaded was either UNIBR176.0500.zip or UNSIGN_UNI1.7.6.0500.zip.. I'm not sure which (I'll post again with the exact process).
The process and files worked perfectly for about 18 glorious hours. My GPS paired, my stereo headset paired, and everything seemed to be working perfectly. The next morning, everything was still working perfectly. When I went to leave work (and use my GPS to find a restaurant), I couldn't power on the bluetooth radio. Whenever I clicked on the bluetooth button, I once again got the "insufficient driver memory to start bluetooth radio" error. I hadn't added or modified anything since the night before (I was afraid to mess anything up).
I have just returned from dinner and am in the process of restoring a Sprite backup (which I love) and will try to recreate my success. I'll report back tonight, and again in 24hrs -- hopefully this time the solution is longer lasting.
I have been trying to get this to work on my trinity--any tips would be welcome.
Frustratingly, I'm back to getting the memory error below. Even if I hard reset, and JUST load up the bluetooth driver (none of my other apps) it no longer works. It must have been a complete fluke that it worked for those 18hrs. I'm going to try again tonight - recording my steps exactly - in hopes that it either works, or that someone can pinpoint my error.
I am fairly sure that the fact that this installation was designed for another device isn't helping me get this working - hopefully I'll stumble across the solution.
I got the hermes version installed ok but it would never pair or detect a bluetooth device. you can get around the memory error by cleaning out your today plugins and getting SK tools. Use the SK tools to stop cprog.exe, then compact heaps and free memory.
ok, I've made some progress and will try and summarize here (sorry for the slow reply). These things are listed in this order for a reason, if I don't do them in order, then the driver won't load:
Hard Reset Palm
Install mNotes (to device)
Install Google Maps (to storage card)
Install Sprite Backup (greatest program ever) (to storage card)
Install Braodcom Bluetooth Stack (see procedure and file location above) (to device)
If I install Google after I install the bluetooth stack, I get the out of memory error (and I couldn't correct it using SDK tools). Also, this setup is kind of finicky about soft resets, occasionally the bluetooth driver won't load, but this is resolved by simply resetting the device.
Things that don't work (that did work under old stack):
Bluetooth Activesync
Voice calls through my sony stereo bluetooth headset
Things that now work that didn't work before
My bluetooth GPS receiver now works
Stereo quality from MP3s is vastly improved (noticeably)
Hopefully someone will come up with a Broadcom stack designed specifically for the Treo 750 - I'd pay for it.
If ayone else has any tips, please post here.
Thanks,
Gavin
I've yet to get the stack to work at all. I have hard reset, installed the stack, used sktools, but no luck. Did you do any other tweaking?
Bump...hoping to hear back on this. I've tried repeatedly and get the same results. I also noticed that it knocks out my microphone on the phone so I cant even make calls when I install the widcomm stack. I swear I am going to chuck this 750 and get an 8525.
Same result as gmctavish
Stack worked great until suddenly radio could not load. I tried installing in safe mode but I get the same results. Maybe if you use a 3rd party task manager and stop the BT service and then install this it will work? I'm going to try.
Very intermittent but when it works it works good.
I had success adding some functionality by using http://www.jetwaremobile.com/
I used it to allow phonebook and call log transfer to another application...Streetdeck (streetdeck.com).
I now can use my car pc to dial/receive calls.
sorry this response took a while. I did not do any tweaking beyond what I described above. Sorry I can't be of more assistance.
I've been working with the Broadcom stack installed for almost two months now - I have several ups and downs I can report.
The Good
The driver itself loads after 90% of hard resets (when it doesn't load, another hard reset gets it to load -- this is strange)
My Bluetooth GPS receiver works (the original reason for me trying to use the stack
My stereo headset works for listening to music and TV shows
I've got a bunch of software installed and I'm not getting out of memory errors (mNotes, google maps, tom tom, bee line, TCPMP, Sprite Backup, PDAnet)
Association/Discovery is UBER painless, I turn on the headset or the GPS receiver and they pair with the phone without any fuss.
No dropped connections
The Bad
Listening to the bluetooth headset with the bluetooth GPS receiver connected and feeding data to either tom tom or google maps is unbearable - 50% of the music is dropped
Activesync over bluetooth doesn't work
I haven't been able to get the phone paired with my computer to use the phone as a bluetooth modem (using junefabrics PDAnet)
My stereo bluetooth headset works fine for audio (some skipping and not great sound, but it works)... however it no longer works for making calls - as soon as I try and make a call it is dumbed to the handheld.
Hi all,
I have posted this question also over a 4winmobile as I cant access xda-dev from work. Hopefully someone here can help.
I've been having difficulty with my Kaiser and a Parrot MK6000 car kit. I have tested the carkit with a Nokia as well, and have some results to report to aid in troubleshooting.
The Nokia was paired with the Parrot MK6000 kit, answers and makes calls and streams audio no problem. When the car is turned off, the pairing ends, when the car is started again the pairing starts back up ... auto, no probs. In addition, if you make a call with the phone, at the end of the call the pairing is ended, but within a few seconds is re-established.
On my Kaiser, I can pair the phone and car kit, but if the connection is lost (ie the car is turned off or bluetooth is stopped on the phone) and then I turn the car back on, it will not automatically pair. It attempts to, the car kit mutes the car radio and plays a tone, but the pairing is not established by the phone. It continues to do this every 30 seconds or so, but does not establish a connection.
Also, if I make a call with the phone when it has been sucessfully paired, on ending the call, the phone will not re-establish the pairing.
My conclusion is that all of my troubles relate to the fact that the pairing will not re-establish once lost.
Is anyone able to assist? I have upgraded the Kaiser radio to 1.27.12.32 (yes ... just tonite, see http://forum.xda-developers.com/showthread.php?t=349528&page=2) but have also tried radio roms 1.27.12.11 and 1.27.12.17 with no success. The ROM version is 1.81.861.0. Ive also tried installing some of the BT stacks that were developed up for the Hermes with no success. I've also installed Jetware with no sucess.
Getting very frustrated!
Adam
adamcullen said:
Hi all,
I have posted this question also over a 4winmobile as I cant access xda-dev from work. Hopefully someone here can help.
I've been having difficulty with my Kaiser and a Parrot MK6000 car kit. I have tested the carkit with a Nokia as well, and have some results to report to aid in troubleshooting.
The Nokia was paired with the Parrot MK6000 kit, answers and makes calls and streams audio no problem. When the car is turned off, the pairing ends, when the car is started again the pairing starts back up ... auto, no probs. In addition, if you make a call with the phone, at the end of the call the pairing is ended, but within a few seconds is re-established.
On my Kaiser, I can pair the phone and car kit, but if the connection is lost (ie the car is turned off or bluetooth is stopped on the phone) and then I turn the car back on, it will not automatically pair. It attempts to, the car kit mutes the car radio and plays a tone, but the pairing is not established by the phone. It continues to do this every 30 seconds or so, but does not establish a connection.
Also, if I make a call with the phone when it has been sucessfully paired, on ending the call, the phone will not re-establish the pairing.
My conclusion is that all of my troubles relate to the fact that the pairing will not re-establish once lost.
Is anyone able to assist? I have upgraded the Kaiser radio to 1.27.12.32 (yes ... just tonite, see http://forum.xda-developers.com/showthread.php?t=349528&page=2) but have also tried radio roms 1.27.12.11 and 1.27.12.17 with no success. The ROM version is 1.81.861.0. Ive also tried installing some of the BT stacks that were developed up for the Hermes with no success. I've also installed Jetware with no sucess.
Getting very frustrated!
Adam
Click to expand...
Click to collapse
Have you tried these registry tweaks? http://msdn2.microsoft.com/en-us/library/aa915920.aspx
There is a know problem with the Parrot kit and you will find a thread in this forum where a member has contacted Parrrot who replied that they are addressing the issue.
This one my be usefull.
http://forum.xda-developers.com/showthread.php?t=340908&highlight=parrot
NuShrike said:
Have you tried these registry tweaks? http://msdn2.microsoft.com/en-us/library/aa915920.aspx
Click to expand...
Click to collapse
Hi, thanks for that pointer ... most of what is described in that MSDN library isn't in my registry.
Im going to manually insert them all and see what happens.
A
Still no luck
I tried updating the Reg with the tweeks as suggest ... but still no luck. All i get is still the initial pair, but on disconnection, no automatic re-pairing of the device to the car kit.
Im doomed at this stage.
You're not alone. I have the same problem with my Motorola S9 headphones and Microsoft SYNC in my 2008 Ford Edge. Sometimes I have to turn BT on and off a couple of times for it to connect.
agreed
Turning the BT on and off a few times has also be part of my "solution" package.
This really isn't acceptable though. This device should automatically pair up, just like every other BT device does. BT is a protocol that should be adhered to and just work.
I have also tried this on my other WM device. It pairs a little better, but is not great. I've tried compairing the registry values of that device to my Kaiser, but I just dont understand the functionality of the reg settings enough to work out what to change.
Is there some developer out there who can help? This type of problem was experienced by us all back in the early days of the Hermes and this community sorted it out.
Can any developer out there help, like working out a port of the Widcomm BT stack for Kaiser?
a
Interesting. I have a Nokia CK-7W bluetooth car kit and the Tyn II has re-connected/connected to the kit every time. Actually more reliable than my SE K800i. Sorry that it doesn't help you.
Hey Juzzman,
nah, that doesnt help ... but does increase the frustration level!
Seems like you need to have a Nokia component in there somewhere for it to work ;-)
Anyhow, Im still convinced it is a bluetooth stack problem in the Kaiser. I'm going to try flashing one of the AT&T based roms and the other radio version and see what happens.
Cheers
Adam
I've had BT issues with all of my HTC devices, it's very frustrating.
Currently I've got a Kaiser (Orange), E650 (Orange) and a new S730, none of which work on my Pioneer headunit without Jetware.
The Kaiser with Jetware pairs up ok, but the sound is really tinny.
The E650 with Jetware sounds fine, but I can only send 150 contacts to the headunit.
The S730 doesn't pair, haven't put Jetware on it yet.
In the past I've had BT issues with M3100, C600, C500 etc etc.
Why the hell doesn't MS sort out their bloody BT stack!!!
Bluetooth problems
I am having the same problem with my JVC bluetooth unit BT1000. It will pair ok first time, allows me to make 2 calls. Will not the reestablish a connection/pairing. JVC worked fine with my sony erricson and nokia phones. Anyone found a cure to this?
Same problem with the stock AT&T rom (1.27.12.11) with the H700 headset.
Turn bluetooth on it normally sees the headset. If not turn it off and on again to get it to work. Once working it normal looses the connection after an hour or so.
Could it be a BT 2.0 Compliant issue?
I have posted this same problem earlier in xda-deveopers, on htc wiki and aximsite. Many people have viewed and are experiencing this same problem, but no one has posted any solution specific to my problem either. I hope a developer can solve this one for us. Is it a BT stack problem, or a BT 2.0 compliant problem, or a need for an updated ATT ROM to solve this issue? (I currently am using the stock ATT ROM 1.57.. that shipped with my Tilt.)
When I use my Motorola H700 with the Tilt the BT works fine, UNTIL, I use the voice speed dialing from the Tilt. Once I use the voice speed dialing directly on the Tilt, the Motorola H700 will no longer connect. I have to do a soft reset or go through the pairing process again. Once I re-establish pairing again, the H700 will continue to work fine, UNTIL, I use the voice speed dialing on the Tilt. Then we're back to having to do a soft reset to again establish H700 connection with the Tilt.
NOW, I just received a call back from an HTC tech who told me the problem is likely due to the Motorola H700 being only BT 1.2 compliant. He recommended that I try the Motorola H12, which is BT 2.0 compliant, but he could not absolutely guarantee this would solve my problem.
Does anyone know for SURE that the Motorola H12, being BT 2.0 compliant, will solve my problem? Or is there another solution?
Note: I have tried MS Voice Command 1.6 (full version), but the above problem still occurs. I have also tried Jetware, but again, no go. I am not sure that there is going to be an updated AT&T ROM to solve this issue either.
Additional Note: I have also tried other BT devices, such as the Jawbone, and the Plantronics Voyager. All do exactly the same thing as above.
Anyone have any solution? If the Motorola H12 is the solution, that would be great...
Thanks in advance.
I'm having the same problem with my new carkit. Did anyone ever find a solution to this??
So I have a shiny new Kenwood KDC-BT838U and for a $220 dollar toy it is pissing me off very much. It does not automatically connect or disconnect from my phone when powering on or off. Simple fix for that is an app to manually establish connection. a2dp will be running fine, then a call comes in. After the call sound will not work and I get all kinds of connection issues until I just power down the head unit then turn it back on (sometimes a few times).
I tested my kaiser with other bluetooth HU's and it worked fine. Then kenwood was not in the store but I love all its other features and it looks great. I contacted Kenwood support and they said that it is a problem with my phone's bluetooth protocol. I decided to give Kenwood the benefit of the doubt. I want to try the widcomm stack.
Found it here.
http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72
I have read that it works with the kaiser. True? After installing the cab, do I need to delete the MS bluetooth reg key or do anything special?
Any Kaiser widcomm users out there? Can you comment on any issues you have? Thanks!
I went ahead and installed the cab linked above. At first I was getting the out of memory error on boot. I changed the baud rate ([HKLM\Software\Widcomm\BTConfig\SerialTransport]) to 115200 and it appears to be working now. Will report more findings later. If anyone else is using it please share your experiences here. Pretty much all the threads I found by searching were people with the same question and they pretty much all went unanswered.
Wellit only thinks it is working. Kasier would not find any bluetooth devices near by and my computer cannot find my kaiser. I guess I will give up now but if anyone else got it working please let me know.
Oh BTW, don't install the CAB unless you don't mind a hard reset. I was prepared for that of course, but just a heads up.
Been reading it for a couple of months now and learned a great deal. I have a problem and was hoping some experts could point me in the right direction.
I have an '05 Acura TL. The phone will not initiate a call over the hands free if I dial from the phone. I have to dial the number, wait for the person to pick up, press the HF button on my steering wheel and say "Transfer". Then I can talk over the Bluetooth connection. There is no problem with incoming calls, only outgoing. I previously had a Samsung phone and this problem did not occur with that phone.
I am currently on WM 6.1 (the new AT&T Rom released yesterday) and had the same problem with WM 6.0. I was hoping 6.1 would solve the problem but no luck.
Any ideas on how to fix this?
Thanks in advance.
You're not the only with this same problem. I was searching right now in this forum to solve that.
When y try to call from my Parrot, is the voice recorder that inizialize in my Kaiser waiting for a voice command.
Any one have a suggestion?
Different radio?
Where would I start debugging?
I am currently using the Parrot M6100 and the Tilt with one of Dutty's ROMs. My setup will work for a while, however, due to the way my stereo is wired in my car, the Parrot does not turn off, even with the ignition off. Every so often, I have to remove the fuse to disconnect power and then it works fine for about a week. I have tried different radios, but the same result. I tried Jetware and it did not make a difference. From the testing that I have done, it points to the Parrot as being the issue. I am planning to update the firmware to see if that helps. Maybe Accura has a firmware update that could help.
If you go here: http://www.htc.com/europe/SupportDownload.aspx?p_id=13&cat=0&dl_id=60 and download the driver there, it seemed to fix the problem that I was having. I would be in the middle of the call and all the sudden it would just drop. I tried it today after installing patch and haven't had any problems.
Hi all,
Need help with my HTC Diamond. As my Pioneer car navigation, with which the diamond bluetooth functioned well, was stolen, I was advised to mount a JVC navigation system NX7000 with a detachable front in order to prevent theft. However, the HTC bluetooth dysfunctions. It connects and pairs without problems, but when the diamond goes into sleep or is switched off, it is impossible to establish a phonecall using the JVC car-unit, although it indicates that blueconnection is still valid. When I switch on the phone, even minutes later, it will eventually do the call. If I force the HTC to remain powered-on it will function normally. I am sure that this has something to do with a suspend-mode of the diamond bluetooth part and that this can be solved by the right registry tweak. I tried several tweaks that I found on the forum already but without succes. I upgraded the HTC to the latest firmware 2.03 but no improvement.
I called with HTC and they said that they know the correct registrysettings but they won't supply them because of "licence restrictions"...........
Anybody the same problem? Somebody who has the solution?
Thanks
I have exactly the same problem! Incoming calls work fine, but like you, I cannot initiate outgoing calls from the JVC unit unless the diamond is turned on fully. I there's not a fix for this, I may have to go out and buy an iphone again after selling mine to get a diamond!
there is a fix but HTC won't tell. they suggested to open a thread on this forum in order to get suggestions on the matter. and so I did. When I subsequently asked them if they would post this solution on this forum they said they would not :-(
Bluetooth problems across the board with JVC NX7000
drpellypo said:
I have exactly the same problem! Incoming calls work fine, but like you, I cannot initiate outgoing calls from the JVC unit unless the diamond is turned on fully. I there's not a fix for this, I may have to go out and buy an iphone again after selling mine to get a diamond!
Click to expand...
Click to collapse
You may not want to fall back on an iPhone with the JVC NX7000. Not to go too far off-topic here, but pairing an single iPhone works great (once I figured out the overly complicated menus). BUT...it won't let me pair a second phone (of any kind). Once the first phone is paired, all pairing menu options are greyed out ("Search" and "Open"), thereby preventing any further phones from being paired. I first need to unpair the first phone before I can pair the second one. JVC Support is comically unhelpful.
Has anyone had luck paring more than 1 phone (of any brand) with the JVC NX7000?
You are the lucky one! You can succesfully pair one phone but it works
I don't care if I can only pair one phone. I only have one phone! lol.
Hey guys!
kind of the same problem here but with the Volvo built-in bluetooth solution. Actually when the device sleeps and I initiate a call it will take some time, then the device will turn on and it will begin to dial but drops immediately. When the device is fully turned on there is no problem at all. Incoming calls work just fine. Even though it first rings on the phone and after a second or two it will ring in the car and the device will stop ringing. Which confirms that bluetooth sleeps somehow and only connects fully when the device is fully awake.
It really looks like bluetooth goes to sleep, so we need a solution which keeps bluetooth awake even if the device itself is in sleep mode.
Patrick
Exactly the problem I described. It's a sleep or suspend mode of the bluetooth that causes the dysfunction. I can pair nokias wih JVC without any functional problem, they work like a charm. It is really a HTC related problem, I tried a lot of registry tweaks suggested for similar problems in other HTC devices, but no luck so far.
Reply to Guitartng:
storing multiple bluetoothdevices in the JVC for subsequent use can be done by selecting "new device" and then go to "bluetooth setup".
Exact same issue with a Kenwood DNX 8120 double din unit.
If anyone finds out the solution, please post it here. I'll keep searching.
Good News Lads!
Well after blowing my head of trying different roms and radios got a solution.
The solution comes from JVC stereo and not from Htc diamond Phone!
You have to set special phones To Samsung E520 and then pair device with the htc diamond. It works like a charm, know I can make calls through my JVC stereo and NO MORE deep sleep of htc diamond.
Try with samsung, it work for me, if not try with other phones in special phones before pairing!
Cheers!
I just wanted to let you know that I also was able to fix my bluetooth issue by flashing stock firmware 2.03.405.3 WWE with Radio 1.09.25.23. I was previously using Dutty's V4 which is based on 2.03 afaik, but it look like Dutty tweaked something on the bluetooth stby behaviour.
Anyway, it works like a charm now and the whole calling and answering process is also much faster!