Hello Folks, wondered if anyone can offer any thoughts about this problem;
( I have searche and read a considerable number of threads on here about this, but none has helped)
MTCD GS type Xtrons running Android 5.1.1
Have had the unit in my car for couple of years, running fine, but slow booting and a bit laggy (old hardware spec, 1gb RAM etc.)) so started looking into rooting / ROMs / MCUs and how to manage performance.
First thing I did was to root it, whilst still on original ROM, which was fine but then noticed the beginning of my problem;
After rooting, and after an overnight / cold restart (i.e. not just a suspend) the unit has lost it's bluetooth settings, and once booted even when the settings are re-entered (both name and PIN) and checked that they have saved, there is no way to get a BT connection for the rest of that session.
The unit can not be seen by other BT devices, and it does not see any devices either.
I've tested with multiple other BT devices to confirm.
I then set about trying a MCU update (2.70 now) which looked like it worked, but turned out to only work the very first time / first session immediately after the update.
Any subsequent restart / new session has the same lost settings and no response no matter what.
Then I tried a couple of ROMs to see if they had a better BT handling ability (although suspect that's stricktly MCU?) so used Hal9K (very good ROM!) and da-anton 1.3 (as that is based on the same Xtrons GS, just modded for speed of boot) but all behave the same way;
Very first major wipe / reset brings BT back and works perfect all day, UNTIL you stop long enough for cold restart, then settings lost and no BT functionality.
These ROM test did at least make me realise that a full factory data wipe (from the android system menus) on any ROM will have the effect of restoring BT functions for ONE session only.
Finally went back to original ROM just in case, but no change to problem.
Throughout all this the Wifi has performed perfectly, instant connection and no lost settings ever, so I don't think I have a hardware fault as (a) the data wipe always brings BT back and (b) I think BT and wifi are the same shared chip.
I did strip the unit and the 725 type combined chip is SMD type on the motherboard, no daughter board or pins / sockets / cables to come loose.
So my questions are;
1)Can this problem be caused by rooting only? or what / where is likely to cause this type of lost BT settings problem, with no effect on wifi at all?
2)Is it the MCU only that handles BT, or any part of the ROM too?
3)IF I give up on BT completely, as I only ever use it for phone connection (but is essential for that) is there any other way (wifi or USB) to link the phone to the unit and get audio (at least) and ideally the phone app to run automatically?
Audio-only would actually be fine, as my phone is in a charging cradle and just as visible as the unit.
Any help much appreciated.
Thanks,
Richard.
Related
OK new to this forum, but please assist if possible - I have an XDAIIs which I have combined with a Bluetooth GPS unit and Bluetooth headset, I am runing the latest ROM from the O2 web site and the following occurs:
with TomTom vs3 the headset will pair but fails to connect, with TomTom vs5 the headset set will pair and connect, but when I terminate a call on the road using the TT vs5 the GPS disconnects at the same time. I have tried TomTom vs 3 with the GPS driver rolled back to vs2.06 which was the concerted opinion of pocketgps.co but that to did not work. I have tried setting the XDA up for a wired conection but that to fails to work - does anyone have a TomTom nav working reliably with this device when it is combined with a Bluetooth headset, any help much appreciated as I am now considering returing the unit as not fit for the purpose it was sold to me - in anticipation many thanks Mike
I have had the same problem with TTN3 and headsets not working. The GPS pairing was not the issue. Removing TTN3 restored the link, but for some reason headsets will no longerconnect automatically.
I have tried soft and hard resets, and updated the bluetooth drivers to build 3900, but still the headsets will not connect automatically, only manually..
I have exchanged a few e-mails with the guru's at TomTom who now thick this may be a bug, but no resolution yet...
OK try this for good measure, I loaded up TomTom vs5 again yesterday, and connected up a wired GPS unit through the serial port (remove cross from check box marked "receive incoming beams" in the Ir port settings tab - in order to use serial GPS) and it works the Bluetooth headset is fine and doesn’t mess up the GPS - However before you rush out and purchase TT5 please read on. Last night I undertook a trip from Blackpool to the centre of Liverpool, approx 55 miles and about one hour in duration. The XDA required soft resetting no less than 16 times on the way there - not easy when driving !! When I got there I needed to use it as a phone and got the no noise in headset problem - note I was not using the bluetooth at this point it was back to a "normal phone" (occurs on my unit at least three times per day) - another soft reset. One other observation with the XDAIIs was its inability to charge up properly when running in the car cradle I set off with 85% in the main battery, a hour later it was down to 35% even though it was showing charging, way too many bugs in this unit for me to consider putting up with it any longer, one month on from purchasing it is going back to the shop and I don't want it repaired, or swapped for another one - I am going to go back to a standard phone that will work, I am sure under the trading standards the unit would be viewed as unable to perform the function for which it was sold - its a shame I like the design of the unit, and the functionality without having to carry around a plethora of kit, chargers, holders etc. but I will return back to my trustworthy ipaq-4700, in twelve months I have never hard reset, the XDA has had over twelve hard resets in the one month of ownership - regards all - Mike
OK appologies for the rant and rave, yesterday I took the unit back to the O2 shop who really did not want to know anything about the problems - "you only have 14 days - take it up with customer support" - which I did, first lesson if you have any problem with a new O2 unit get it back in the 14 day period. Customer support were most helpful and aventually agreed to replace the handset with an identical machine at the local shop, which proved easy (shame about 40 min on the phone but at least I got somewhere) second lesson use the support system it really does work. thirdly the shop assistant manager informed me O2 are no longer selling the XDAIIs with the TomTom package due to neumerous problems - that says something in its self. Loaded the new unit up with TT5 and used it today for navigation (3 hours), no problems with charging, GPS or phone usage all day, if this remains the case I will be a happy customer, perhaps I had indeed been supplied a faulty handset, time will tell - Mike
sinclox, if you need more advice on this one please e-mail me on [email protected]
I am sure you can get it to work - I am most impressed with my unit once the bugs were ironed out - let me know _mike
Mike,
Thanks for the offer, currently I am waiting for TTN5 upgrade to arrive until them I am unable to register TTN3 due to the TT upgrade process and so can't use TTN on the XDA.
I have dumped the O2 active interface in favour of Wisbar 2 and the XDA hasn,t locked up since.
Have you any clues as to how to get the bluetooth connection working automatically again with headsets? :?
Send me an e-mail to address previously posted on this link - Mike
I purchased marbella GB-6205 V2.2 for my dopod900 but pairing problem is encountered.There shows ? in the icon. I'm running out of tips. ROM 1.30.230WWE. Somebody got any advice
Dont really have a tip i just wanted to see what people came up with. I am haveing the same problem with my Gsat 359. My issue is with the 8525 and Wayfinder. im on VP3gs offical wm6. Also having issues with some of the menus looking like half circules but that is more an issue with the software.
For both posts, I think that you have to be more specific, not being able to pair a device might have lots of causes, in example:
- Are you sure that your devices are indeed in pairing mode, having them to enter in pairing mode can be tricky sometimes
- Usually any device in pairing mode within range will be detected by the PDA/phone.
- Sometimes the keyboard applet appears just above the passkey request window not permitting to see it (happens sometimes with my universal), also there are at least two "common" paskeys used for bluetooth devices (this doesn't mean that some more could exist), usually "0000" and "8888".
- Are you sure that both (PDA/phone and bluetooth device) devices work? Try to pair another bluetooth device with your PDA/phone and try to pair your BT device with another PDA/phone; defective items are always a possibility.
- You might even have had success to pair your devices, the problem might be the software, see all the post that To_mT_om have generated because of problems with third parties BT GPSs, verify your software and a very practical way of being sure that everything went ok with the pairing is to install the app that usually all BT GPSs have included, normally a very simple app that displays geodesic coordinates or even raw NMEA info.
- Some PDAs/OSs might have the need to "create" another serial port for the new BT GPS in order to be accessed by the software, also see the other posts for this information.
Do you need more info?
Verify all the possibilities, perform all the test mentioned and then be very specific about the exact problem, most of the best gurus (and I'm not talking about me!) ask for a tough research of the forum's posts before asking for something that might have been already answered, I understand them when they say that it is not funny to answer to the same question (in various flavors) several times.
One last thing, it's holidays time, many people could be missing in these days.
Good luck
got mine up and runnning. My problem was software related. Downloaded software from handango and i just wasnt working right. Went to the manufacture website...wayfinder.com and the new software found my gps with no problem.
We've tended to find that simultaneously restarting the BT GPS and PDA at the same time (and often with a battery removal on the GPS) can solve issues where the GPS simply doesn't want to complete pairing.
When this fails, it's usually software related or a corrupted Bluetooth stack / registry settings on the PDA..
Worst case, hard reset the PDA..
Good luck
Andy
www.pressdigital.com.au
Press Digital Support Team
I have problems with my Bluetooth and the paired device in the car with almost every recent ROM.
After about 10 minutes driving with a connected phone, the Bluetooth shuts down on my Diamond. When I go to Settings -> ... > Bluetooth -> Mode -> Turn on Bluetooth is unchecked. If I check it again it connects again with the phone and about 10 minutes later it's off again.
I went back to the RUU_Diamond_HTC_WWE_EastEurope_1.93.479.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe. It's against my feelings, believe, etc. but I want to solve it .....
I installed Advanced Configuration Tool (3.0), went to Bluetooth -> Audio gateway power save and Disabled it. I did it because I was reading about suspended devices and power save features. I thought that the loss of Bluetooth is been caused by a saving power feature.
After a soft reset, the Bluetooth stays connected.
It's a start, but I'm not happy with it ... I would like to use cooked ROM's and optimal settings in the ROM.
There are other tweaks too in Bluetooth, for example the supported bitpool, etc. Perhaps those settings cause the shutdown of a connected Bluetooth device instaed of the power save feature.
Has anyone this kind of problems too with paired Bluetooth devices?
If so, would you like to help me to find the cause?
If not, can you describe what device you use (Jabra, TomTom, car radio, etc.), which ROM, which radio and extra tweaks?
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
olliver said:
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
Click to expand...
Click to collapse
I have a CD70 too in a Opel Zafira.
This "comm manager" thing is interesting, but it looks to me like an Opel issue.
Can't you flash firmwares by opel?
Riel said:
Can't you flash firmwares by opel?
Click to expand...
Click to collapse
That's an option, but my Trinity (P3600) performed great with the same car. Will an upgrade solve my problems? I know one thing, it's not cheap either.
I tried it with different ROM's, but it still happens.
I tried it with different radio's, nothing changed.
Till today, I've got now the new radio (v1.05.25.BS14).
http://forum.xda-developers.com/showthread.php?t=432770
It has fixed the delays in GPS + faster GPS fix and more important fo me Bluetooth didn't stop today.
I'm sure 100% sure yet, but seems to be better.
I got something to complain too about the new radio. The radio signal is less strong than the .05 radio.
Same problem here
My Vectra is equipped with CD70.
Previously I've owned a Kaiser and the problem was solved by one of the 6.1 radios, bluetooth connection was rock solid.
Right now I have the same problem with Diamond - after every single phone connection, when I'll hangup, the phone disconnects CD70. When I'll try to reconnect manually using CD70 everything is fine.
I've noticed that the same problem exists when I'm using Nokia bluetooth headset - one call, bluetooth connection dropped...
I've tried following Diamond radios:
.05
.07
.08
.BS14
and two Raphael radios by Bepe:
1.03.25.18
1.02.25.11
Each Diamond radio behaves the same way. Each Raphael radio adds a bonus - random bluetooth connection problems.
Right now I'm back with .05, I think I'll look for the software I've seen once (can't recall the name) - it's a PDA application designed for connecting to the car bluetooth systems and it has been cerftified to work fine with CD70.
Use Jetware Mobile for htc-diamond.
jetware
That's the software I couldn't remember the name.
Anyway I gave it a shot and it gets even worse, I couldnt get the connection lasting longer then 2-3 minutes, totally unstable
Right now I got back to radio .08 - the bluetooth link is rock solid, I guess I'll just need to get used to reconnecting after each phone call
Same bluetooth system in my car, same problems as you guys.
To avoid the disconnections after calls you need to go, with 'Advanced Config' to bluetooth->Audio gateway power save, and switch it to disabled.
For me this little change solve the 'first' problem, but I have another one that I don't know how to solve: the aparently random bluetooth disconections. Sometimes BT is not disconnected in hours, sometimes in days.
I am also using Jetware Mobile, but i didn't feel any improve...
The random ones depend on the radio rom version - I was using .05 and it was rock solid.
I will try .16 with audio gateway started and with power save disabled as you advised - I thought about it earler but previously I tried to disable the power save without enabling audiogateway service
Well, we will see if it works or not.
Hi,
I also have a Vectra CD/70 combination, for 2 yrs now.
I had a HTC3300 and 2years i had not a single problem with Bluetooth connection.
Now i have a HTC Diamond Touch Pro and have the same problems you guys have.
I tried all your suggestions, radio's and so on with no good result.
The good news is .. its an Opel problem and it seems to be that a Bluetooth Firmware Upgrade is available from Opel Germany. I just contacted my dealer and next week he will Upgrade my bluetooth firmware.
I will keep you guys informed.
Hello,
had the same problem with my Opel CD70.
Using Jetware Mobile and limited the entrys who copied to the car to a max. of 5. Also disable the call lists. Now it works.
I think the Opel/Vauxhall Bluetooth Connection disabels if to many entries are copied to the car.
Hello,
any News about our Bluetooth Problem ???
I also have a CD70 from Opel and I cannot understand why my Diamond swich of Bluetooth after a while ?
Is it an Opel-Problem or does anybody now an Application which helps ?
Thanks a lot for Your help,
Stepos
Hi,
I am currently using BTrestore (http://home.casema.nl/rgschmidt/WM/Downloads/BTRestore_V_1_0_0_PPC.ARMV4.CAB). This utility checks the status of the bluetooth stack every 5 secs and (re)enables it everytime it's down. It seems that the 5 secs are short enough to keep the phone connected. It's not a real solution and unfortunately this tool is sometimes instable too, but it absolutely extends the connection time with the UHP.
Maybe bullock can tell us if the carkit upgrade solves anything...??
I also created a ticket at HTC, but they refuse to troubleshoot user specific issues. They told me they only look into issues if they get enough calls from different users and to keep an eye on the update site (they seem to be able to solve issues without knowing what the actual issue is...). So I would encourage everyone here to create a HTC ticket for this issue. I still think it is an HTC issue: a bluetooth stack should never go down without any user intervention.
Good luck!
BTrestart and Jetware Mobile doesn`t help, my Touch diamond disconnect again from Opel CD70 and swiched off Bluetooth !
Can anybody help ?
Sorry guys, the OpelDealer is still "searching" for the Bluetooth upgrade.
After several phonecalls maybe next week (1st week of Febr) it will be made available to the dealer.
Like i said ... i willl keep you informed ... still have this lousy problem !!
..does anybody use the new Rom 2.03 ? Any difference ?
I also asked my Opel-Dealer for an Update of UHP, next week I 'll get new Information....
... well guys I had my CD70 updated !! I am/was very sceptical because the only thing they did was a re-install of the Language of the Navi System with a version 2005 CD. I asked if that was all to correct my Bluetooth problem .... the (smiling) answer was YES.
I have it now for 24hrs ...... and Bluetooth is still on )
I will let you know the result after a week !!
..i can't beleave it works with a 2005-update ! Great !
My Opel-Dealer is still busy in selling 10 Opel Corsa every day (..the magic word is "Abwrackprämie") , so I'll have a date there next week...
When I bought my Vectra the dealer had also to reinstall the Language-CD, maybey it was the wrong version....
...... Sorry guys ......
This update DOES not do the magic trick !! So we have to find another solution
who has the right idea ??
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
radak23 said:
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
Click to expand...
Click to collapse
Hi, I am using my Touch Pro 2 with the same HU and Bluetooth adaptor as you but no such problem so far.
It used to have this problem then I try to connect using Window CE as the phone setup and choose another Connection Key instead of default 0000 to pair the phone with the HU.
ok, well i just tried connecting via searching for the device from the HU. it finds my device - i tap enter (to connect on HU) then it just jumps to a blue flashing 'connecting' then goes to a yellow 'error' straight away. if i select 'open' on the HU then it connects (connecting with a different ID - a number '6') but only untill i restart the HU.
also as a test i just tried an Xperia (just had one laying around LOL) and it does the exact same as mine!! ARRRRGHHH!
so im glad to say i believe it is not an HTC issue!
ok so i have an update - the problem is my HU will not pair correctly and it will not store a pairing. great.
another quick one - have found others are having trouble with their HU/adapters. thanks anyway everyone!
TP2 Bluetooth and voice dialing working fine ???
Have you tried to reset your carkit? I had the same problem after the rom-update with my TP1 and I put my carkit (Bury CC9060) back to factory settings. So I did the same this morning after I updated my TP2 and now it works just like a charm. Of course I don't know if your carkit has this possibility. Good luck, greetz Ton
'iznogoooog' - yes it work perfectly until you restart either device - 'ton66' - unfortunatley a reset is pretty much all i can do!!! eeeeek!
hopefully a reset will fix it! - i did unplug my b/tooth adapter then switch the unit on - then off then plug it back in.. didnt change anything.. oh well! will do complete re-set 2day!
BTW:
thanks so much for everyones help!
Got a questions. I am using the AVX-826 with build in Bluetooh. I want to know if you guys get the Signal Strength show on your Head unit is correct. on my unit pair with TP2. The Signal Strength indicator doesn't move. it always show the strength with my phone is connected to the unit and it stay that way.
The Battery Strength indicator does work and show the correct battery level.
I have exactly the same prob!
Hi,
I have a AXV800 and a BTA200.
My first device was a Artemis with WM6.0. No problem so far!
Then I changend to a Diamond with WM 6.1 and had the same problem as mentioned before. Now I tried my new TP2 and still the same problem.
And I tried the old Artemis again with a new 6.1 ROM and the same problem as on the other two phones.
Now I think it depends on the WM build. 6.0 seems to work 6.1 not!!!!!!!!!!
I did a reset on my AVX800 two times without luck!
I think I'm going to use a normal phone without Windows mobile for the next test!
Schelbi.
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"