imate 1.72 Bluetooth keeps reverting to Discoverable mode - MDA II, XDA II, 2060 ROM Development

Since upgrading to ROM 1.72, my Bluetooth control panel keeps reverting to the Discoverable mode. I want it to stay in the ON mode. It seems after I go to Bluetooth Settings it will revert to Discoverable as well as when I do a soft reset. What the heck?
Is there a registry hack to fix this?

adam,
thanks for helping me out with pocket msn. it is a pretty cool service.
i also have an i-mate. this was happening to me before and after the rom upgrade. so i don't think it is something that was introduced with the lastest rom.
i am very fed up with the the primitive bluetooth features on the i-mate. i can't get it to work with my jabra 250 bluetooth headset. using it as a bluetooth modem works sproadically at best. although i can use bluetooth activesync pretty consistently.

I am not sure if this has anything to do with it but have you deselected beams under settings/connections/beams? I am not sure if that operates on both bluetooth and irda.

Ah, deselecting recieve incoming beams seems to fixed it. That does work for Bluetooth.
@Jonlien, mine's the opposite. It works flawlessly with a Bluetooth headset, but Activesync rarely works. Activesync doesn't reconnect via Bluetooth if the system has gone into standby mode or the Bluetooth USB adapter was removed/replaced at some point.

adamz said:
Ah, deselecting recieve incoming beams seems to fixed it. That does work for Bluetooth.
Click to expand...
Click to collapse
Actually, that didn't fix it... still keeps reverting to Discoverable mode. *sigh*

Related

Pocket Bluetooth Tools: need help

Hi there! I have an MDA II and a Parrot CK-3000 (with sw ver. 3.13) carkit. I read about the outcoming of this sw and I decided to install it on my MDAII. But, after a correct installing procedure, it simply doesn't work: my carkit remains mute like a fish!!! :shock: I'm asking you, guys already use successfully this sw, a hand of help to solve my trouble (if possible). Note that I downloaded it from this
http://bluetooth.i-networx.de/index_e.html
and I tried to follow all the instructions placed in there...
Thank you all!
pap
paperuccio said:
Hi there! I have an MDA II and a Parrot CK-3000 (with sw ver. 3.13) carkit. I read about the outcoming of this sw and I decided to install it on my MDAII. But, after a correct installing procedure, it simply doesn't work: my carkit remains mute like a fish!!! :shock: I'm asking you, guys already use successfully this sw, a hand of help to solve my trouble (if possible). Note that I downloaded it from this
http://bluetooth.i-networx.de/index_e.html
and I tried to follow all the instructions placed in there...
Thank you all!
pap
Click to expand...
Click to collapse
Why not email the author, he is most helpful.
Had the same issue with the Parrot. My Plantronics headset works a treat, but not the Parrot.
I mailed the author who confirmed there are some problems and a new release will be needed.
As the author is doing this work unpaid and the functionality is so good, I can wait.
@ mrg2003
I send an e-mail some days ago but still had no response.
Anyway, I agree with IanF and I'll wait for the new release.
I wish I read this bulletin board more often.
Yes, I have exactly the same problem with the CK3000 (v3.13) and PBT. HBH-35 works a treat but CK3000 does not bond (XDA thinks it does but there is no handshaking and CK3000 repeats request to bond).
Back to basics again ...
Incidentally, does anyone know if Tobias plans to engineer a way to trigger Voice Command and take input from the car microphone for voice recognition? Would be the dogs and well worth a major donation ....
Cheers
I've had some problems with pocket bluetooth. I have emailed tobias as follows and am awaiting a reply. Was wondering if anyone has faced similar problems:
Tobias,
Thanks for all the hard work in getting these tools working. I have just bought an XDAII with the latest 1.60.00 ROM using the 1.10.00 radio version.
At the same time, I have a WIDCOMM bluetooth dongle on my PC which supports numerous profiles including the headset profile, which allows me to use the PC's speakers and mic as a 'headset' with the XDAII.
I set up the XDAII with the PC, using the built-in bluetooth bonding and pairing application and managed to get it all working fine with the PC using the speakers and the mic as the headset, with the phone automatically transferring the call to the PC when the 'Bluetooth Headset mode is enabled' shows on the today screen. Furthermore, activesync also seems to work fine too.
After installing Pocket Bluetooth Tools, the headset stops working. Before installing it, I unpaired the device by deleting it from the list of paired devices. After installation and going through the process of pairing the device again, it correctly gives me the option to choose the Serial Port, ActiveSync, Modem, and Headset profile. I select all of these and click on OK. Once this happens, my PC gives me a message saying that the XDAII has connected with the headset. However, this doesn’t happen once but goes into a continuous loop giving me notifications every 2-3 seconds that this is the case. Furthermore, when making a call to see if the voice has been transferred to the PC< this stops working and the XDAII's speaker and mic continue to be used. The only way to stop the constant loop of connections is to switch off the bluetooth radio on the XDAII. Furthermore, when deleting the pairing from the XDAII this constant loop continues.
Have you faced this issue previously, as I think it may be a bug. The only reason I installed pocket Bluetooth is that my current b.tooth headset is a Nokia HDW-30 that supports the handsfree profile and your documentation states that Pocket Bluetooth tools supports this profile.
Let me know if there is a fix for this.
pap[/quote]
Why not email the author, he is most helpful.[/quote]
maybe just because he doesn't answer
i wrote a very long report some days after the long awaited new version came out in april, but haven't got any reply. (maybe my email got lost - who knows ...)
i have exactly the same problems. i also have a parrot ck3000 (tried with firmware 3.11 and 3.13) and an mda2 with rom 1.6.00GER and extROM 1.60.07. the two devices pair, and sometime i can even select the "headphone profile" afterwards. i even managed to make it work ONCE, after several hours, of installing, reinstalling, pairing, reparing, ect, ect ...
what did work once was making calls. but after the first call came in, i could answer it, the caller could hear me, but i couldn't hear anything. this happened twice and then i just turned off bt and used the mobile as always.
as i'm using my mda in my car for work and not for fun this is no solution for me . i went back to the original bt stack that works quite well. i can make and take calls w/o any problems.
one thing i'd like to see changed (as soon as parrot and mda work together) is, that ALL calls are made via the handsfree, as, as long i'm in the car it HAVE TO use the handsfree by law (and it's much more comfortable anyway). it's not practicle to dial with the mobile, and then by pressing the green button on the parrot to move the call to the handsfree. but that's the only way you can do it when using speeddial.
another thing i desperately miss is a way to change the volume of the handsfree. i could do this using the volume slider of my nokia 6310, but volume stays all the same when using the mda. and it's just too low when doing higher speeds on the autobahn
of course voice dialing would be a great feature to have ... but it's not that necessary.
please don't get me wrong .. i'm don't want to be ungrateful as i'm not paying for this software - i just want to help ppl by saying that they are not alone with their problem and they should give up wasting their time and better wait for a new release....
and of course i'm very willing to PAY for that software as well as soon as it is any improvement over the original bt stack (for me of course. for most of you it already is)
maybe TOWA could say some words here. that would be really appreciated.
thanks anyway a lot to all ppl that spend their free time developing software and providing it to the comunity!!! thumbs up !
regards ize|man
Bluetooth tools and ROM 1.72
Does ROM version 1.72 require TOWA's bluetooth tools? In this ROM, there are options for COM port selection etc under Bluetooth settings and the clubimate site mentions bluetooth improvements. Anyone with this info?
other com settings then
Inbound COM port com4
outbound COM port com5
??
if so what are they?
Rudegar
You are right. Inbound 4, outbound 5. Likely required for GPS devices, if i am not mistaken
faisal said:
Rudegar
You are right. Inbound 4, outbound 5. Likely required for GPS devices, if i am not mistaken
Click to expand...
Click to collapse
These are the ports for BT beaming, as I understand! (not for BT GPS).
For BT GPS you do not specifically need BTHTools anymore (since 1.66) because WM can install a BT GPS com at first bonding.
Something is different however (vs BTHTools) since with 1 application (Alturion) I can not get the BT GPS working anymore, which can also not be solved by still installing BTHTools!! (while I have no problems with my other application TT. Figure that out?!)
Ronald
I now have the same problem, the parrot ck3000 was working until I insatlle dthe bluetooth tools, and now it doesn't.
Its a shame I did not see this thread before
Will the 1.72 rom work with both parrot and my emtac bluetooth gps?
Cheers
Justinp
justinp
have you tried uninstalling Bluetoothtools?
no not yet, I might give that a go, but then my gps wont work :?
justinp said:
no not yet, I might give that a go, but then my gps wont work :?
Click to expand...
Click to collapse
I think it will still work!
With my working application (TT3) I see the GPS on COM5 (installed by WM) + on COM7 (installed by BTHTools) + on the BT/SIRF interface!
If I uninstall BTHTools I only loose the selection for COM7. The other two selections still work!
Of course you must have acknowledged the WM com installation with first bonding (in any case for the serial operation)! My BT/SIRF connection always works in TT3 regardless of WM/BTHTools installation of serial ports.
Ronald
I'm also having that strange problem with the parrot CK3000. I did install the previous version of BT but I don't see any difference with or without BT. But when I de-install and want to go back to the original state, the same problem persist. Is there any way to download anyware the original Bluetooth stack without re-install everything (and loosing all my settings and software)?
Thanks for helping out.
Frank.

No bluetooth connect when wifi turned on?

Hi everyone. I recently noticed an issue whereby if I have my wifi turned on, my mogul won't connect to my car's bluetooth. I usually have it off but often when I insert the phone into my seidio car cradle the wifi switch turns on and the bluetooth doesn't connect. As soon as I turn the wifi off the BT connects fine. If I switch wifi back on BT goes off again. Weird. Not sure if this is interference or a software issue. I am on DCD 2.1 rom. Anybody else? Any way to have the Mogul ignore the hardware wifi switch or assign it a different function? Thanks.
Mogul wifi
I have the same problem wiith the stock 2.17 ROM
A reasonable work around is to go into comm manager and just turn wlan off. Have to do it after each soft reset though. Overrides the hardware switch which is what I need.
ive never had this problem (currently using 2.2.6 but 2.17 was fine too)
i do know the 2 share an antenna though, could be an issue
Wifi and bluetooth at the same times works fine even before the leaked ROM stuff.
I use the Slingbox via WiFi and listen via bluetooth all the time.

Jabra 320 A2DP problems...

Hey people,
I tried connecting my Jabra320 up to my Touch HD the other day. The headset should support A2DP for stereo bluetooth, which worked with my old Touch Dual, however, whenever I try adding the headset to my HD I can only see the hands free profile.
Anyone had any problems with A2DP or any ideas how to fix this?
I was thinking about getting a Sony Ericsson headset, but don't want to commit to the investment until I know that I can use the A2DP profile...
I'm using Dutty's v2.5 rom and the v1.12 radio.
Same problem with new duttys roms. It shows me both wireless stereo and handsfree but when i try only to connect A2DP it disconnects. Worked fine on older duttys roms.
I have Jabra 620s
tunppi said:
Same problem with new duttys roms. It shows me both wireless stereo and handsfree but when i try only to connect A2DP it disconnects. Worked fine on older duttys roms.
I have Jabra 620s
Click to expand...
Click to collapse
You're getting a little further than I - I domn't see the 'Wireless Stereo' option at-all. Well I believe Dutty is releasing a new ROM soon. Hopefully it'll be fixed then. If not I'll mention the problem when it comes out - hopefully Dutty or someone will find a fix.
Thanks though for confirming I'm not the only one with this problem!
Hope you guys has fixed your problem. if not, let me tell you how to fix it.
I had the same issue before. now it works.
1. make sure your headset is power off and delete the connection on your cellphone.
2. connect your charger to the headset for 4 seconds, then disconnect it.
3. repeat step2 4 times.
4. after that, your headset will be reset. then, reconnect to your cell phone and you will see wireless stereo function enabled.
What I have discovered on my A2DP headphones (Philips SHB7100) is that when I power them on it will automatically connect but only with wireless headset (phone calls only) functionality.
What I have to do is go to the touchflo settings tab, select Menu> Bluetooth Devices and disconnect then reconnect the headset. Once I do that it connects for both A2DP and phone calls.
I also have a Jabra "Dogtag" headset and it ALWAYS reconnects with both automatically unlike the Philips set, so I suspect this also has something to do with the headset itself and not just the OS/ROM.

[Q] Bluetooth Headset not pairing ICS LPQ

So my Jawbone Prime was connecting fine before I updated to ICS LPQ (was on GB LA4 before) and now it doesn't even show up on the devices list even when I try to re-pair or reset the headset.
I tried 2 different sets to no avail.
Anyone know of a solution?
Connects to A2DP BT Headset (Motorola) but only allows media audio to connect. Phone audio doesnt stick.
ICS has some compatibility issues with certain bluetooth devices.
GB my phone always paired with my car stereo and streamed music without any issues.
So far every ICS release, even official, has caused my phone to reboot after streaming music over BT for 10+ minutes.
Its pretty sad they dropped the ball here. GB worked fine, and they borked it.
Well I can connect my BT keyboard fine. I just tried my Motorola BT earphones which are A2DP and it connects but won't allow phone audio to go through the BT earphones. However Media does go through. At least it detects it.
It doesn't detect it at all on the Jawbone Prime (which is not A2DP).
Update:
I managed to connect my jawbone and actually have 2 phone calls on it. After that I had the phone in my pocket and when I checked maybe 15mins later it had frozen and I had to keep power pressed to shutdown/reboot.
It kind of matches Chakker3D's pattern of working then not working. It's like there's a memory leak in the bluetooth stack? maybe I'm just spitballing here.
What I know is that in GB whenever I deactivated BT it took a good 20-25secs. In ICS it's instant to turn off or on. In GB however there was 0 issues.
I just really hope Samsung addresses it. Or if we are lucky, a dev will rework a rom so this problem is gone.
But from what I can tell, very few are having this problem.
Airbag888 said:
So my Jawbone Prime was connecting fine before I updated to ICS LPQ (was on GB LA4 before) and now it doesn't even show up on the devices list even when I try to re-pair or reset the headset.
I tried 2 different sets to no avail.
Anyone know of a solution?
Connects to A2DP BT Headset (Motorola) but only allows media audio to connect. Phone audio doesnt stick.
Click to expand...
Click to collapse
Sometimes is helps when you change kernel. Give a try
078gregory said:
Sometimes is helps when you change kernel. Give a try
Click to expand...
Click to collapse
Another update:
Without any intervention on my part other than keeping on trying it finally discovered my BT headpiece. In fact it discovered both.
Now it's still not 100% perfect because it discovers it, connects and immediately disconnects. If I press a button on the headpiece while it connects then it stays connected and it hasn't restarted/locked the phone yet. I even connected my 2nd headset (another Prime) and it worked.
Keeping fingers crossed. Now I need to see what happens when I walk out of range and back in range.

[Q] Bluetooth Autoconnect

I'm guessing the answer to my question is likely to setup a Tasker profile, but I thought I'd ask anyway. Does anyone know of a way to get Bluetooth on my OG to autoconnect to a device it's already paired to?
For example, when I get in my car and want to connect to my stereo, I turn on Bluetooth, then have to go to my paired devices and manually connect to the stereo. I'd much rather just turn on Bluetooth and have the phone autoconnect to the stereo.
I'll likely soon set up an NFC tag for my car, so I should be able to turn on Bluetooth and connect to the stereo with that, but wanted to know if there was another solution in the meantime.
Any ideas?
Digil said:
I'm guessing the answer to my question is likely to setup a Tasker profile, but I thought I'd ask anyway. Does anyone know of a way to get Bluetooth on my OG to autoconnect to a device it's already paired to?
For example, when I get in my car and want to connect to my stereo, I turn on Bluetooth, then have to go to my paired devices and manually connect to the stereo. I'd much rather just turn on Bluetooth and have the phone autoconnect to the stereo.
I'll likely soon set up an NFC tag for my car, so I should be able to turn on Bluetooth and connect to the stereo with that, but wanted to know if there was another solution in the meantime.
Any ideas?
Click to expand...
Click to collapse
As long as I turn on Bluetooth before I start my car, mine auto-connects to my Hyundai Sonata just fine...
Sent from my LG-E970 using xda app-developers app
My phone auto connects to my car too. Even if I forget to turn it on before I start my car and toggle it on after the car has already started, they will find each other and auto connect. They do not connect instantly though (maybe the BT scan interval is a little bit longer). Maybe you just have to wait a bit?
I have Llama installed and have a profile setup so that when it disconnects from a known Wifi (leave home/work/etc.), the phone will turn on BT automatically and try to connect to the car. Another profile is set up so that once the BT does connect to the car, it will turn off Wifi on the phone and also turn up volume and vibrate "on".
Hmmm, thanks for the replies. I'm wondering if my issue is that I've only turned Bluetooth on after the car was running, not before. If anything, I'll just set up a Llama or Tasker profile. Thanks again!
Digil said:
Hmmm, thanks for the replies. I'm wondering if my issue is that I've only turned Bluetooth on after the car was running, not before. If anything, I'll just set up a Llama or Tasker profile. Thanks again!
Click to expand...
Click to collapse
Yeah, if I turn on bt after I start the car then it won't auto-connect.
Sent from my LG-E970 using xda app-developers app
Just a heads up to anyone interested. Tasker doesn't have an action to autoconnect to paired Bluetooth devices. However, there is an app available in the Play Store solely for this functionality:
https://play.google.com/store/apps/...sMSwyLDEsIm9yZy5teWtsb3MuYnRhdXRvY29ubmVjdCJd
This app is also a Tasker plugin, so you can use it in conjunction with any Tasker profile. Good stuff.
Digil said:
I'm guessing the answer to my question is likely to setup a Tasker profile, but I thought I'd ask anyway. Does anyone know of a way to get Bluetooth on my OG to autoconnect to a device it's already paired to?
For example, when I get in my car and want to connect to my stereo, I turn on Bluetooth, then have to go to my paired devices and manually connect to the stereo. I'd much rather just turn on Bluetooth and have the phone autoconnect to the stereo.
I'll likely soon set up an NFC tag for my car, so I should be able to turn on Bluetooth and connect to the stereo with that, but wanted to know if there was another solution in the meantime.
Any ideas?
Click to expand...
Click to collapse
I have a very similar issue. I have two bluetooth devices in my car. My handsfree system and a stereo adapter. The phone autoconnects to the handsfree system but I have to manually click on the stereo adapter every time to get it to connect. No ordering of on/off etc seems to alleviate this. Any ideas?
themoe said:
I have a very similar issue. I have two bluetooth devices in my car. My handsfree system and a stereo adapter. The phone autoconnects to the handsfree system but I have to manually click on the stereo adapter every time to get it to connect. No ordering of on/off etc seems to alleviate this. Any ideas?
Click to expand...
Click to collapse
The app I mention above has an option to autoconnect to all paired devices. This might be what you're looking for.
Digil said:
The app I mention above has an option to autoconnect to all paired devices. This might be what you're looking for.
Click to expand...
Click to collapse
Yea, already gave that a shot. Tried just the app, then tried a tasker profile that would try to connect to the A2DP device if the handsfree device was connected too. Neither worked. Gonna try another couple apps to see where it gets me; if not I'll just live with having to always click it in the settings menu until an AOSP rom comes along that I would be willing to run (not quite annoyed enough at the LG software to give up an SD card/8gigs and hardware keys)
themoe said:
Yea, already gave that a shot. Tried just the app, then tried a tasker profile that would try to connect to the A2DP device if the handsfree device was connected too. Neither worked. Gonna try another couple apps to see where it gets me; if not I'll just live with having to always click it in the settings menu until an AOSP rom comes along that I would be willing to run (not quite annoyed enough at the LG software to give up an SD card/8gigs and hardware keys)
Click to expand...
Click to collapse
Try this app. Have been using it for a long time now. I have the same problem as you. You can set it up to automatically connect to a second device ( your music adapter), right after it connects to the first one ( your car). There are also more useful settings there.
https://play.google.com/store/apps/...nav_result#?t=W251bGwsMSwxLDMsImEyZHAuVm9sIl0.

Categories

Resources