Hands Free Car Kit - Won't Connect Anymore! - P3300, MDA Compact III Accessories

Hands Free Car Kit - Won't Connect Anymore! - P3300, MDA Compact III Accessories

I've been trying to get my MDA Compact III working with my built-in car bluetooth hands-free system (Land Rover Freelander 2) for the last 3 weeks or so with varying degrees of success, but I think I've messed something up...
Until the weekend, I could enter the PIN my car generated into the phone and it would spend several seconds trying to pair; sometimes it would, sometimes it wouldn't, but it would always take several seconds to make the effort. However, now as soon as the car generates the PIN, it goes straight to "failed to connect", the phone doesn't even give the chance to enter the PIN and shows no indication that anything's tried to connect to it.
Is there anyway I can "flush" my bluetooth settings without a hard reset? I wasn't doing any registry tweaks, the only thing I think I did before it went wrong was selected the "set as hands free" on the list of connected BT devices on the phone.
Any help greatly appreciated!

Related

TomTom lock up

Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...

I am still on my S100 with tt6 6.010 (7720) and no SIM since I currently use it solely for navigation. What I experience is not really a lockup but just a big delay (almost 1 min) after tt has initialized and only if "Enable wireless data" is enabled.

UPDATE
Turns out that this was a system resource problem. I have Wisbar 2 Advance, PocketBreeze 5, Phone Alarm, and PhotoContacts Pro all active on my device. I guess this is just too much to handle for the Omap when I try to add TomTom on top of that. When I exit WA2, PA and PhotoContacts, shut the device off for about 30 seconds, then turn it back on and launch TomTom, I have no problems. I have also been able to do it only shutting down WA2 and PhotoContacts, but it still locks from time to time like this. I have to shut down all three to be safe. Leaving PocketBreeze running (with some plug-in tabs active too) seems to be a managable workload for the processor. It's kind of a pain, but at least it works! It's not like I need a nav program every day!
Later...

Glad to know you found the source of your problem.

psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??

Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?

Magic Button - Pocket PC Task Manager
This will CLOSE the program instead of MINIMIZING it to the background process.

JC#79 said:
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Click to expand...
Click to collapse
I only started putting things on the card two days ago - day two i started having tomtom problems.
I'll def give this a go though and let you know if any improvements...
Thanks!

i have the exact same problem with my dopod p800w/artemis etc etc......i found a way to eliminate the freezing and hanging.......rule of thumb is to open the program by going into its root directory and opening it from there, instead of opening it via the start/programs shortcut or today screen......basically just make sure you open the program by going into File Manager and look for the tomtom navigator.exe file (usually in the program files folder and then navigator folder) and open it that way......ever since i tried it this way i never get any freezing and the program would start all the time.......it works for me......

Bluetooth problem with TP2 and Acura HFL

I have a Sprint Touch Pro2 running stock 6.5 ROM and a 2005 Acura TL. When I got the phone a few weeks ago, I was able to pair the two without problems and it persisted reliably. I was able to shut BT off and turn it back on and the pairing would take place immediately.
Four or five days ago, though, the pairing would drop periodically, forcing me to re-pair, and now, the pairing will disappear almost immediately if I'm able to get them to pair at all. Most of the time I can't get the phone to 'see' the car.
FWIW, I use my own 4-number PIN, and when the phone sees the car, I'm able to enter that PIN and pair them.
I of course was installing a lot of stuff on the phone, although nothing that one would expect might affect the BT, so I flashed back to the stock 6.5 ROM last night to see if it helped (it didn't- same prob today).
Before I take this thing back to Sprint and smash it on their counter, anyone have any ideas about settings I might not be aware of that could affect this?
Thanks in advance for any help.
PS: I'm going to be testing my old phone (Treo 800w) on the car later to see if it still pairs to eliminate the car as the problem.

[Q] CyanogenMod RC4 & nightly Bluetooth pairing problem

Hi,
I can't post in the dev forum (not enough posts), so I've stated a thread here. Wiht RC4 and the latest nightly I have a problem with Bluetooth pairing. When I attempt to pair to a selected device (either another phone or my car system), I get the pairing pin dialog displayed and ca start to enter the pin, but the keyboard is only displayed for approx 10 seconds, if I try really hard I can get a simple four digit pin entered and the pairing works, but for other pins there is not sufficient time! It seems as if there is some sort of timeout that is not long enough. If I just leave the pin dialog displayed (without the keyboard), that will also be removed after 10 seconds.
I'm using the latest radio firmware (same problem with older versions), and I've tried using the older rll file from the dev thread (no change in the problem).
Is anyone else having this problem? I'm currently grabbing the source from the github to try and work out what might be going on, but it seems a slow process. Let me know if I can provide any further information.
Andy

Hi,
So can anyone confirm that the pairing dialog works fine for them with this rom?
Andy

Hi Andy
Yes pairing works with my iPhone 3GS (Jailbroken) but will not connect. I think that in my case it is the iPhone that is at fault because it would not connect to my previous LG mobile although it paired ok.
Stransky
(Douglas Barr)

Hi Thanks for the feed back. If you have time could you try the following. Remove the pairing from your phone and then try pairing again. I assume your Wildfire will display the enter pin dialog box. If so just leave it one the display. How long does it stay there for? On my phone it only stays there for about 10 seconds. Does it stay displayed for longer than that on your phone?
Thanks for your help
Andy

Well I've managed to get my phone paired with my car. Basically by typing very very fast! That way I can just get the pin entered in the ten seconds available. So I can now use cm7. Would still like a proper fix for this is anyone has one. I did take a look at the log files but couldn't see any obvious errors...
Andy

Dear all :
I have same problem with my Streak 5
I'm try to pairing but no connection with car bluetooth
a you can help me on my e-mail please :
[email protected]
thanks to your help

Trouble with 2012 Honda CR-V and Bluetooth - Current Fix

So Sunday I rolled into our family favorite Honda dealership, and I rolled out with a 2012 Honda CR-V AWD EX-L. Didn't get the Navigational system, as per reviews it looked outdated and cheesy, and I have the Galaxy Nexus official car dock with charger coming from expansys any day now.
Paired the phone at the dealership, and was able to play some music. But the connection dropped briefly, causing music to play out of the phone. Then about 20-30 seconds later it reconnected, and a few seconds later the music played out the car speakers.
Didn't think too much of this, but I drove it home and the next day noticed the disconnect / reconnect issue was pretty consistent. And every time it happens, you can't control the Radio or do other things, cause the screens talking about the connection prevent changes. Not life or death, but certainly annoying on occasion.
Yesterday, I determined that by connected an AC Adapter to the phone, the disconnects go away and things work normally. That was a pleasant surprise, and while I don't want to take the phone out of my holster and connect it EVERY time I get in the car, at least I have a work around, right?
The odd thing is, this never happened with my Sony BT Car Deck I had in my Civic. Obviously it wasn't a stock solution, but when the volume knob on the stock deck was failing, a new stock deck was $400. I got the Sony solution for $150 installed at Circult City, and it had bluetooth which allowed me to make and take calls, stream music, etc.
The only catch I've found so far is the car seems to inquire about me transferring my contacts into the car so the phone book is available through the dash. But every time I click allow... it doesn't seem to do anything and the message shows shortly again in the "notification bar" of the phone. I'm ignoring it for now.
I did root the phone and apply the 4.04D update, then the system update saw the 4.04I update and applied that. Wondering if a factory reset might not put me back to 4.01 or something, but might not resolve this issue. Unless I have any advice, I think that's what I'll try next.
I thought about updating the baseband radio, but as I didn't install CMW or anything, pushing the radio update is a little more work that I'm ready for at the moment.
Thanks to any who took the time to look at this. Best wishes!!!

Little update. I had unlocked my phone, but hadn't properly rooted it, flashed the ROM, etc. Took me a while this morning, but I rooted it, installed CWM on the recovery partition, and then updated the radio to UGLA4.
Despite the above, the car still "drops" the BT connection about once every two minutes, and then makes the connection again about 10-20 seconds later. If the phone is plugged into the car so it has extra power, the connection stays up and reliable until it is unplugged or the car is turned off.
Not sure what to try next, if Honda doesn't have a BT update for the radio in this car. Here's hopiing!!!

FIXED!!! So here is the problem AND the solution.
Dunno why, but something about the default bluetooth.apk that is in the Galaxy Nexus, even after the 4.0.4 update was NOT working between my phone and my CR-V.
The "hint" to the fix was found here. http://forum.xda-developers.com/showpost.php?p=14249943&postcount=11
After killing this process, my connectivity issue between phone and car disappeared. But the phonebook STILL wouldn't update.
Feeling I was getting somewhere, I did searches for the BluetoothPbapService, and so forth. After some looking, I finally found THIS site. http://forum.android-rsap.com/viewtopic.php?f=33&t=221
I had unlocked my phone once, but hadn't rooted it properly. While trying to fix this issue, I'd rooted it, installed the CWM recovery menu, and tried a couple different "broadband" software packages that control the radio. That hadn't fixed the problem, but I COULD use Root Explorer with SU rights afterward.
So I downloaded the file for Android 4.0 to the Downloads folder on my GN. Then I created a new folder on the SDCard called backup. I moved the Bluetooth.apk and .odex files that were in /system/app into that directory, moved the .apk file I downloaded from that site back into /system/app, and made sure the permissions were as directed. Then I rebooted the phone.
Once down at my car, I removed ALL Bluetooth profiles from the car, clearing the BT settings completely. And then I deleted the BT profile from my phone. Then I turned on BT on the phone, pressed the phone button on the dash, and paired the phone as before. Only THIS time, the phone paired normally, didn't disconnected, and when I clicked phonebook, it seemed to do nothing as before. But a SECOND click on Phonebook, and instead of trying to download again... I GOT LETTERS to lookup names!!!!!
I tried a couple calls, and people didn't answer, but I can call and use the BT in my car normally!!! OH HAPPY DAY!!!

Took the CR-V in, got my proper plates put on, they washed the car for me (looks great!), and I ran a few errands. Having sat around doing laundry and watching Batman Begins, I wondered about getting the Media option on my Galaxy Nexus to disable like I'd tried in the past. That way, I can listen to the radio, but if I'm using my turn-by-turn directions over Google Maps, I can her Nav instructions through the phone.
I did a BUNCH of searching, and lots of people had similar issues. But one one had found a way to disable the "media" part of the Bluetooth stack. Remembering some people found that killing the PBAP process of the Bluetooth stack in Apps allowed them to sync their phone to their car, I wondered if it would help with my media issue. So I disabled it and went down to the car.
At first, there was no difference. Media went through the car, and nothing was any different. I unpaired the phone from the car, cleared the car BT setup from all devices, and started over. Once again it popped up as it always had, and I tried telling it NOT to pair every time automatically, but don't pop the HandsFreeLink message. This didn't seem to work, as the phone would disconnect and reconnect as it had in the past.
Frustrated, and ready to give up, I cleared the pairing on both sides, and went to put it back how I started. But when I cleared the car and went to pair again, I added my Galaxy Nexus, and waited for the message to come up about pairing going forward. It never came. And ironically, the car was NOT paired for media, just the phone.
Feeling brave, I connected the phone to the car with the media checkbox. It connected, and I was able to play a song through the car stereo. Figuring it wouldn't disconnect, I tried anyway... and it DID! I then turned off the phone, and off the car. Turned the phone on, the car back on, and everything KEPT working!!!
Obviously, I need a little more testing to be certain. But lt looks like I may have stumbled across a setting or something that allows me to use the phone however I wish. And that is a VERY good feeling.

Have no issues in a '12 Civic. You know, other than the recall.

Well, I'm back to having trouble.
Upgraded to Jelly Bean. Love the voice search which works great for me, the speed is still excellent, etc. But even after replacing the bluetooth stack the way I did in 4.0.4, I can't permenantly disconnect bluetooth audio for MUSIC through the phone. I've tried the usual fixes as above, and it just ALWAYS stays connected, assuming the car is on, and bluetooth on the phone is enabled.
SO FRUSTRATING, as then I can't listen to the radio AND use my turn-by-turn directions!!!

The wife and I have been troubleshooting this problem ourselves with weird results.
We purchased GNex's from Bell in Canada at the same time (yakjuux builds). About a month later, we leased a 2012 CR-V. Her phone has always had this connect/disconnect issue, while mine hasn't. We have returned her phone to both Bell and Samsung on separate occasions; all they have done is flashed it and sent it back. Of course that hasn't solved the problem. Provincial law in Newfoundland requires the use of hands-free when on the phone while driving, so this is issue is more than just an annoyance.
I got tired of waiting on Bell and Samsung Canada to get their act together with 4.1.1, and recently rooted my phone and moved it to a 4.0.4 takju build in order to get the system update. No problems with any of that, and it works with our CR-V, same as it always has. We hoped that doing the same to her phone would put this issue to bed once and for all, but after having run hers through the same process this evening, it still does the same trick of connecting and disconnecting endlessly (unless you force-stop the phonebook service, of course).
Now that both phones are rooted, I'm about to try copying my Bluetooth.apk on to her phone and seeing if that fixes anything.

Question Watch refuses to pair with Redmi Note 8 Pro

I had to send in my phone for repair (likely will take a good while since it's the holidays and all) so in the mean time I'm using an old phone but having major pains trying to get these two to work together. I get the FastConnect prompts from the PW app, though it always fails immediately after PIN confirmation, and the watch just mindlessly does that "circle going around the rectangle" searching animation, and the overlay on the phone says it failed to connect, and offers me the option to "open app." As long as the watch animation is going, the PIN codes on my phone just repeat, never going anywhere, so trying again just fails anyway due to "incorrect PIN" as they don't even display on the watch at that point.
Eventually, after maybe 5-10 mins, the watch gives up, says it "can't pair with devices," and presents only the option to "reconnect," which forces a reboot and the process to start anew once more.
I've attempted to pair it with the Bluetooth settings instead, only for it to fail there, as well.
ONE TIME I somehow got it to pair, then when I made it to the step to set up Assistant, it failed twice to do so before I opted to skip that, but it DID finish and I got to the main PW app menu. Unfortunately, I was distracted by something after messing with the Pixel Watch app on the phone, only to look back and see it was "disconnected" and my watch said it had "failed to connect," and now I'm back at square one, with a pretty paperweight strapped to my wrist. I'd like to be able to track my sleep and heart rate for the time being until my phone is repaired. Any suggestions?

Have you reset the watch to factory settings? I can only pair a watch with a fresh reset of the sotfware, I get the offer to connect and link without the reset but it always fails, and I had to remove the watch from the fitbit app as well.

Multiple times.

Develop Bugs

welcome