Related
Hi All,
I have been reading a lot of messages on both 8525 and 8125 trying to isolate the issue and there doesn't seem to be a straight asnwer anywhere and hence I am trying to get the attention of the users here...
I have a pioneer navigation system with a bluetooth built-in. My previous phone (blackberry) and my wife's treo650 both stay connected with car's bluetooth when on call (never a disconnect). But my new 8525 gets disconnected mid-call (usually after 2 to 5mins, but have also seen a disconnect within 1min). That is, it does pair with the car kit and when there is no call going on, the bluetooth connection never dies. This disconnect only happens mid-call, almost all the times.
I have the latest ROM (1,34.502...., radio: 1.16), got the phone about 2 weeks ago from Amazon.com. Called cingular and they say could be faulty phone and I have searched other forums like audi message board where their car kits are also having the same disconnect problem with 8525, so I doubt this is a single phone issue.
I have taken the 'band' hack and forced the phone to be in either GSM or WCDMA mode and in either modes, the phone still exhibits the same problem (there might not be any connection between the two at all, bluetooth with GSM/WCDMA, but thought there might be some weird connection...but not the case thankfully).
I read somewhere about some bluetooth tweaks on 8125, but never found what those were. I need some help here otherwise I am going to return the 8525 and stay away from it. I need the bluetooth to work efficiently.
thanks for all your help
Phal
San Jose, CA
please help
I really need some help, clue or direction on solving or at least isolating this bluetooth issue. I love the 8525 but if I cannot fix this bluetooth mid-call disconnect issue, I will unfortunately have to return, which I don't want.
What headsets the 8525 works fine with (no drops mid-call)? May be that is a starting point.
Please also give me some links to 8125 tweaks that some talked about? pof/other moderators/anyone?
thanks a lot in advance!!
Phal
I have an Motorola H700, and every once in a while it will disconnect, looking at the phone after that, BT is turned off, turn it back on and it works again...
There are problems with the hardware and the API used to access it, good phone, but I don't think it was ready for the market yet when they released it. It is likely to be corrected in the next ROM release, last I heard from Cingular is mid 2007, but by the way things go, prolly around late 07/early 08.
I'm having similar issues with the BT headset I use, which is a Samsung WEP150. It'll drop midcall to the handset. I'll look and BT is turned off.
The only remote correllation I've found is that it seems to occur when I've received a new email or something a la ActiveStink.. And I haven't really been able to confirm that... But I have definitely noticed it happening then though.
my 8525 does this as well with my factory BT in my 05 Acura TL. Kind of frustrating, have not been able to figure it out yet.
Problems w/ Audi BT as well
Same issues with my Audi Q7 BT. I have seen posts in this and other forums blaming the MS bluetooth stack.
My 8525 worked flawlessly with my Garmin NUVI 660, never disconnected or failed to connect automatically. This is frustrating.
8525 Fix
I had the same problem with the 8525 and my Pioneer Avic-Z1 bluetooth kit.
I hacked the registry to force the bluetooth radio to stay ON, rather than going into sleep mode. This seems to have fixed the problem (although with limited testing at this point).
My calls would consistently disconnect with 2-4 minutes. After the hack, I've had 2 45-minute+ conversations with no trouble.
Here's the fix... install a registry editor (like PHMedit), and add a DWORD here:
HKLM\System\CurrentControlSet\Control\Power\State\ Suspend
Add a DWORD called btl1: (note the colon, the colon must be there), with a DWORD value of 2.
Good luck!
My Q7 as well i took the advice of wolfgram and did this to my phone i will let you know how it works it would be a shame to give up this phone but it is really useless if this feature does not work right.
Well this is what i did i did what wolfgram said and it still cut out but not as much so i took the checks off in the advance power mode and never let the phone go to sleep and it works all the time. HTC needs to upgrade thier bluetooth setting not to go to sleep. It must stay active at all times MY phone book and all other info posted into my Q7 with no issues at all and it even sees the bluetooth b4 the MMI system in the car Boots up..
Lance
Resolution I think
I turned off 'Making device discoverable to other devices' and it seems to have solved this problem, I am using the phone with a parrot kit and it kept disconnecting now it works all the time.
Treo 750 doesn't have this problem
Well, hopefully you owners of Hermes have figured out the fix. I had to return it and now got the Treo 750 and can gladly say the problem is not there. The treo 750 has the v1.2, but I guess following the replies here, that possibly Palm fixed the problem by keeping the BT radio on at all times.
In any case, here is the post I wrote in avic411.com forum - if you want to see any follow up responses by other owners..
http://avic411.com/forum/viewtopic.php?p=24170
cheers
Phal
Bluetooth cut out
I am having the problem too with the garmin Nuvi and the Tytn - which is ineresting seeing as how one poster had no problem with the Garmin device. Here is something else that is interesting - I did not have the problem when I had the HTC 1.18 Rom installed. After I flashed the HTC 1.35 Rom, the problem began. I have already tried upgrading my firmware on the Nuvi - that did not help. I also use a Nokia 800 bluetooth headset - and that never cuts out with either ROM. I will try turning off the bluetooth discovery first. If that does not work, will try editing the registry. Keep you posted.
Turning off bluetooth discovery did not work.
Turning Off Bluetooth Did Not Work For Me Either
this worked for me.....
http://forum.xda-developers.com/showthread.php?t=247520&page=10
drains the battery quicker, but no more bluetooth problems.....
Hey guys, has anybody found a solution for the auto turning off of the BT in suspend mode? its gettin really annoying
Hi
I have read through literally hunderds of pages of GPS stuff to do with mini. I have read some things that are true and some that aren't and am now confused.
I installed Tomtom 5.0 onto my Mini S. It went on fine. Maps installed fine. I went into 'satellites - configure' part and couldn't find my GPS on any of the settings. I am almost sure my GPS receiver isn't bluetooth. I know the baud should be 4800, but otherwise I am not sure. My dad has the same recieve but uses his with an IPAQ and it worked first time. I have tried my receiver with his ipaq and the receiver works fine so that eliminates that posibility.
Here is my receiver and the blurb that comes with it.
http://www.evermoregps.ca/
GM-R700 GPS receiver
(third one down.)
The mouse-shape GPS receiver is design for PC and PDA applications. With WAAS/EGNOS channels, EverMore can give you more accurate direction and position. Compact Flash module is also available now.
I selected 'Other NMEA GPS receiver' and tried all of those. Then went through the bluetooth equivelent just in case. None of them pick my receiver up.
I then read somewhere that version 6 of Tomtom wouldn't work on my XDA mini. I downloaded 5.2 and tried it with that. I had read that this allowed 'port 7' to work. I couldn't get my map to work with 5.2 even though I spent ages on it. Eventually I tried Tomtom 6.0. As I mentioned earlier, someone had said that it wouldn't work on an XDA, but this is false as I got it working straight away. The map also installed fine and once I activated it things seemed ok. I presumed that the port 7 would now come as an option. It didn't. I am still at the same place. I believe that the port 7 thing may be a bluetooth only thing but I am not sure. I am not great at GPSbut know my way around an IPAQ pretty well. I am new to my phone so chances are there is some gateway or something that I haven't enabled etc, but I am at the end of what I know.
If anyone can help me out at all I would be eternally greatful. So far I have spent a good 20 hours getting the bloody thing working and I am about to lose the will to live.
I have used the search option on the site, but it seems everyone has BT GPS, and none of the posts seem relevant to my problem. If I have missed a post then I am sorry, but there are a fair few posts on the site now.
Thanks in advance,
Woody.
bluetooth
you have to pair your gps receiver with your phone in bluetooth settings give it com ports then go into tomtom then into show gps status then configurethen other bluetooth gps receiver then pick your com port hope this helps
jay05 said:
you have to pair your gps receiver with your phone in bluetooth settings give it com ports then go into tomtom then into show gps status then configurethen other bluetooth gps receiver then pick your com port hope this helps
Click to expand...
Click to collapse
Do I have to do this even though it isn't a bluetooth device?
Even when I enabled com 7 on bluetooth settings, comm 7 didn't appear on 'Select your GPS receiver' on Tomtom.
I will try it anyway, and thanks for the speedy response.
sorry
i have give you wrong advice i thought gps recever wash bluetooth you should try going into on your phone settings, connections ,beam ,and un tick receive all in coming beams as these frees up the com port 7 on xda1.YOU WILL HAVE TO RECONFIGURE SETTINGS IN TOMTOM GPS STATUS FOR WIRED GPS RECEVER. SORRY FOR LAST POST HOPE THIS HELPS ps i got gps recever recever off ebay was meant to work on my xda1 but did not it was for ipaq the connector was the same but wiring was wrong hope this helps
Woody, first of all I couldn't understand that which GPS device have you got as you have mentioned 3rd down on that webpage, anyway I have the attached the picture of one of the device named "GM-R700", if this is the right device which you have then this is a serial cabled GPS device which connect to the device via cradle, not via Bluetooth, if I am right then bluetooth chapter is closed, we are going to talk about the cable GPS device.
If it is the right device then how are you connecting the GPS device to the XDA, does the GPS device came with the cradle and the car charger? (it must be).
Find the attached word file for a sequential instructions, I have just made it for you and others who are still stuck to make their TomTom work.
GoodLuck & let me know.
Sidd
Sidd, your attached documents refuse to open!, I am not too sure that you can connect a wired GPS to this type of phone, it simply won't work, the only option is Bluetooth for the Wizzard. In the case of the IIi and IIs phones they had a true serial port that could be used - Mike
Try these attached files as I have zipped them on a normal compression.
I think ""GuinUK (1st post)"" hasn't mention his/her device, but the GPS he/she mentioned is a serial device.
Sidd
I am pretty sure it is a Mini S he is trying to get to work with the cabled GPS receiver, it simply will not work - the device doesn't have a serial port to connect equipment like this to. The Mini S is Bluetooth only for GPS AFAIK - Mike
sidd said:
Woody, first of all I couldn't understand that which GPS device have you got as you have mentioned 3rd down on that webpage, anyway I have the attached the picture of one of the device named "GM-R700", if this is the right device which you have then this is a serial cabled GPS device which connect to the device via cradle, not via Bluetooth, if I am right then bluetooth chapter is closed, we are going to talk about the cable GPS device.
If it is the right device then how are you connecting the GPS device to the XDA, does the GPS device came with the cradle and the car charger? (it must be).
Find the attached word file for a sequential instructions, I have just made it for you and others who are still stuck to make their TomTom work.
GoodLuck & let me know.
Sidd
Click to expand...
Click to collapse
Thanks for your reply. This is indeed the right GPS. Sorry for any confusion there. I am about to try what you have written. I have indeed got a cradle, and a converter which makes my Ps2 GPS fit into the socket.
I will get back to you with how I got on.
Thanks again for the help, at least I know for sure it isn't BT before I start.
Woody
mikealder said:
I am pretty sure it is a Mini S he is trying to get to work with the cabled GPS receiver, it simply will not work - the device doesn't have a serial port to connect equipment like this to. The Mini S is Bluetooth only for GPS AFAIK - Mike
Click to expand...
Click to collapse
OK I got the download working from Sidd, thanks. I ran through all the steps you had mentioned. The problem I had is that I don't get the option of 'serial cable blah blah', mine just says 'Serial port'.
My phone is a Mini S. Perhaps this is the reason why. My friend has a bluetooth model, and I got that working fine so I guess if this last attempt doesn't work I will just buy another GPS. It isn't like they are expensive in truth.
Thanks everyone for the help, and sorry for my delay in posting but it being Xmas and all.
Cheers
Woody
If u r going for a bluetooth gps device then keep one thing in mind that u might find difficulty in searching of the proper bluetooth com port. Soltution is to download the TomTom version 5.2 prior to connect ur device.
GoodLuck & let me know
Sidd
Fantastic post
Thanks Sidd, your word doc (Serial COM Port setting to setup TomTom.doc) worked a treat, two mins and I'm up and running. I'm using spv m1500 (same as xda 2) with a cheap unbranded cabled gps unit i got from fleabay and TomTom 5.2. Thanks again.
Can I re-iterate for the benefit of others reading this post, the newer XDA device (equipped with a mini USB connection point) cannot be used with a wired GPS unit, this includes the Mini-S, Exec, Orbit etc. The older devices IIs, IIi etc all require the Receive all beams to be turned of to free up the serial port for use by the wired GPS.
If your device has a mini USB connector your only option is Bluetooth for GPS - Mike
Doc114 said:
Thanks Sidd, your word doc (Serial COM Port setting to setup TomTom.doc) worked a treat, two mins and I'm up and running. I'm using spv m1500 (same as xda 2) with a cheap unbranded cabled gps unit i got from fleabay and TomTom 5.2. Thanks again.
Click to expand...
Click to collapse
No problem Doc114 my pleasure, any way I am also going to upload something new on the FTP (check in: ftp://ftp.xda-developers.com/Uploads/Software/) with another brief instruction manual, enjoy the new one, you know what I mean (My name would be included in the file name, so you can recognise it easily).
I will also make one illustrated instruction for a bluetooth GPS setting whenever got a device.
Sidd
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its speaker works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
CJSnet said:
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its output works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
Click to expand...
Click to collapse
I do have exactly the same problem. After flashing XDA Mobile 6 Release 3, microphone has worked for couple of days, and then suddenly died. Interesting, microphone is working with Notes but not with phone. I went back to
XDA Mobile 6 Release 2 for some other reasons (read: 2MB more free memory for critical application) but the problem with Bluetooth microphone remains. Radio is 2.25. Any advice?
--
Pogo
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is sometimes temporarily resolved for a short time. It always comes back though
I have been asked to join this thread. Per a PM:
We love the ROM you have provided, and are very thankful, however it was not until installing it that this issue arose. It does not seem fair to leave a number of people with a phone that is unusable for 'phone calls'.
Click to expand...
Click to collapse
(Bolding added by me)
I don't know what to tell you. If the rom doesn't work for you, then don't use it... Don't tell me its "not fair". I use MS Voice Command, and XM6r3 and have never seen this issue with my Bluetooth headset (Jawbone). I've also tested this out with a Plantronics Explorer 210 headset that I have and it has not problems with XM6r3 either. My A2DP headset (Spider) also works fine on XM6r3 with MS VC. I've stated this in the past when people have said they have BT issues on my rom. Sorry, but I can't reproduce it, so its hard for me to fix something that isn't broken for me.
Try this... Do a hardreset on your device (take a backup first if you want), then leave it as the base rom with NOTHING extra added. Run that way for a few days (how ever long it has taken before) and see if the problem happens again. If it doesn't then its not my rom but something being added to it (probably screwing with the registry someplace). If it does happen, then as I've stated before, I've seen a number of BT devices be flakey on WM6 (especially car kits). Try a different rom then. If someone with the problem can pin it down, I'll be happy to do what it takes to fix this issue if its something in the rom that is causing it.
Thanks mfrazz. What wasn't fair was not the bug, but that you had not responded to previous mentions of it, i.e. not fair to leave us with it. We love the ROM and put a lot of our life in your hands in a way, as we rely on our device so much for work and play. Hope you understand.
Now then, I have already tried a hard reset and the problem never occurs, until WM6 is put back on. Sure, 'use another ROM' is all very well, but we love yours - again, hope you appreciate the sentiment. If you're in a relationship, are you the kind of guy who tells a girl who loves you, 'find another boyfriend', or do you try to make it work
SO, I am wondering if this is related to the glitch you mention where sometimes when switching out of vibrate mode, the ring tone becomes muted. For that, your solution is to play the ringtone again, then it becomes unmuted.
Similarly, our Bluetooth devices mic's are being muted, and if we mute then unmute them again, then they become unmuted. A link that helps point you in the right direction?
Please note, this is not certain bluetooth devices being 'flaky', this is ALL devices. 4 at the latest count, including rock solid Nokia CARK7W car kits and Jabra headsets.
Some people put it down to MS Voice Command, which I have never installed. What does that program do, do you know, to cause the bug? Again I hope that might help point you in the right direction.
Please don't dump us Let's try to fix what is wrong in this relationship
BT problem solved?
CJSnet - not sure if you have resolved this. I was having the same problem and noticed people with reTouched dialer were not, so I loaded that dialer and the problems went away. I am using a Plantronics Voyager 510. Seems the problem might be with the standard dialer.
Hope this helps
CJSnet said:
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is temporarily resolved for a short time. It always comes back though
Click to expand...
Click to collapse
Thanks, I'll give that a try. However WM6 has pretty much finished the Wizard for me, and I'm hoping to get a TyTN II soon as a replacement. Shame.
Hello,
I have recently bought the Parrot Minikit bluetooth speaker but it seems that there is something wrong with connection between it and the touch cruise.
pairing is performed with no issues but when i want to make a call it RANDOMSY sometimes transfer audio yo the Parrot minikit but sometimes it does not and the call stays in the phone (which of course makes me unable to hear...)
I really do not know what to do. i have tried several ROMs and several Radios (including the original ones) but it seems the problem is consistant with all of them.
Please of anyone knows if there is someway to solve this problem make some bluetooth patch to the polaris or an alternative bluetooth stack i can install that may help ... or any other suggestions...
Please Help
Thanks
Same problems here. How can I downgrade to BT 1.2?
Hi guys,
This problem was handle before. Just look in http://forum.xda-developers.com/showthread.php?t=437888&page=4
Succes
WAS
Have a stock unrooted N4 running the new 4,4,3.
Updated to 4,4,3 solely in the hope it would solve the bluetooth disconnects experienced. Note I did not have 'stuttering' or the like, just solid disconnects which would then auto reconnect in 30-60 sec unfortunately stopping my music app which would then need to be restarted and since I primarily use the BT on my bike or motorcycle it is obviously a pain ....
!!!!!!!!!!!! the update not only has not stopped the disconnects it has now introduced stuttering on occasion (not all the time) ....
Here's where I am at:
1. Live with it until Google finally realizes IT'S A PHONE not a camera or whatever and solves the BT problem or gets the BT folks to do it. (really can't believe they can't solve this or is it just an N4 problem?)
2. Root the phone, install TiBU, backup, wipe and install 4.4.3 factory images, reroot and recover stuff from TiBU ... all this in the hope the BT problem goes away ... chances of this?????
3. Give up and install CM which people say does not have this BT problem ... true??????
Thanks in advance to all for your help and opinions ..........
Could it be
Could it be the BT device itself? Does it work like a charm with other devices?
Electrospaz said:
Could it be the BT device itself? Does it work like a charm with other devices?
Click to expand...
Click to collapse
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4
zdrifter said:
That's a great question and I am sorry I did not include the info in my original post ... the problem is evident with several different BT devices and these same BT devices work fine connected to other things ..... but not with the N4
Click to expand...
Click to collapse
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..
Electrospaz said:
Has it always been stock? Perhaps your BT adapter in the device is faulty itself. I've ran two different headsets off of mine in the past year as well as connected to my PC and other phones with no issues at all. I've been rooted running beanstock right from day 1 though..
Click to expand...
Click to collapse
Yup ... always stock ... when new on whatever version was current then (can't remember) did not have this problem and BT worked fine ........ when they went to the 'low power' BT solution it started.
Was really hoping this update would solve the disconnect problem.