Hi
I have a parrot handsfree MKi9200 installed and it's been working fine. But since 3 latest updates on my S II, it's been acting odd. I'm now at version 4.0.4.
Problem is when connecting to the parrot it's ´stuck for some 20-25 seconds. When it's done doing whatever it's doing i get a message on the phone in a grey boks.It's in danish, but it's something about bluetooth has stopped syncronization. I have to press OK on the phone to get grey boks to dissappear. This also happens if i call someone and obviosly at some point hang up, then i get that odd message again and phone is stuck until it has done "something". On the display of the parrot device, i see the symbol for sync running while it's going on.
Is it some Bluetooth setting i need to tick somewhere that has been enabled within last 3 Android updates?
Cheers
Rathsach
It maybe that the parrot bluetooth software needs updating. Check your manual to see how to updae the software.
Bluetooth updates on the phone download newer versions of the sofftware which may not be compatible with the version of the parrot.
Related
I've installed the newest version of Pocket Bluetooth Tools on O2 XDAII with latest O2 ROM release. Two problems:
- the XDA II does not go into standby mode after answering a call
- bluetooth remains active instead of switching off after x minutes (the clock on the screen is white).
What am I doing wrong ?
Thanks,
Can I just bump up this question again. I'm very happy with Pocket Bluetooth Tools, accept for the powerdrain caused by bluetooth being on. PBT is supposed to switch is off automatically after a minute, but I find, even when it goes all the way around and goes completely white, bluetooth does not switch off.
Has anyone else found a solution to this problem? Im using the latest rom from O2 (1.66 I think).
Regards
Surur
I am running 1.66WWE latest version of rom on my XDA ii and the latest bluetooth tools and it shuts down bluetooth perfectly, it counts roudn getting greyer and at the end it goes fully white and the blue light stops flashing to indicate that bluetooth is turned off, however the XDAII's bluetooth section still reports it as on and the headset symbol stays enabled, but if i press the button on my headset i cannot get into the phone screen so it is definatly working on mine,
It must be another piece of software stopping it powersaving on your one, or something wrong in the registry maybe?
Hi,
I know many have problems with Bluetooth and certain car kits. I specifically have a VW. In any case, my Galaxy disconnects from not only my car, but also from my Philips in home audio system. In both cases, the disconnect is the same. What happens in both cases is the Bluetooth pair is lost. If I try to turn off and then on the Bluetooth (on the phone) to reset the pair the Bluetooth light never fully turns on. It stays a dim green. To get it to work I have to restart the phone.
I wrote a script to collect the Bluetooth logs, and programmed it to start logging whenever Buetooth is connected. Attached is my log. notice that around 7:56 the probem occurred. I was in a call on my galaxy s2 connected to my vw tiguan, and the hands free audio stopped. I was able to pick up the phone and switch from hands free to the speaker (on the phone) to resume the call.
Around 8:19, I think, I turned off the Bluetooth on the phone, and then tried to to turn on it again. But,it did not fully turn on. The green Bluetooth light is dim rather then bright. The only way I can restart the Bluetooth is to reboot the phone.
There are exceptions thrown that I am going to look at.
Have any thoughts?
Thanks!
I am running the stock rom that I downloaded from Kies. The Android version is 4.1.2
Logs:
1. S2 paired with VW Tiguan (7:56, 8:19 approx) https://www.dropbox.com/s/hd809geb4hoxvrr/btlog.txt
2. S2 paired with Philips AS351 (Time 21:02-21:06 approx) https://www.dropbox.com/s/6w7je0xrdcn7kiy/20130916_902-906btlog.txt
Follow-up
I have spent quite a bit of time over the past few weeks testing different Android versions, testing Bluetooth Keepalive, speaking to other developers, logging errors and debugging, installing different versions of Cyanogenmod, and speaking to Samsung.
In short here is what I have found:
1. The problem still exists in the stock rom that is downloaded from Kies with Android version 4.1.2.
2. Problem was still encountered, and potentially worse, on Cyanogenmod 10.1 with Android 4.2. (Problem happened more frequently)
3. Still testing with Cyanogenmod 10.2 with Android 4.3, and so far I have NOT had any issue.
4. I have had mixed results with Bluetooth Keepalive, but have been in contact with the developer.
I spoke with Samsung yesterday as well as last month. I requested a call from a developer, but they would not allow. They said they would connect me to the next level of support, but I would have to wait on hold for an hour. Oddly enough, I did not want to or have time to wait an hour. However, over the coming days I am going to contact Samsung using a more direct method in hopes of speaking to a developer. The tech guy I talked to seemed to indicate that it was his position that it was a 3rd party issue, and I should contact my auto manufacturer. I explained to him that this problem happens across multiple auto manufacturers, and the one common theme is the Galaxy phone. In addition, my auto manufacturer has replaced everything Bluetooth related, and has had no issue testing with other phone models. The Samsung rep also said, and I agree, that sending the phone into Samsung for repair would be worthless.
Short of rooting your phone and installing CM 10.2 with Android 4.3 the problem still exists. Again, I am still testing with CM 10.2, and look forward to speaking with Samsung again.
I have a Cubot One, using the G800_CUBOT_D1_V0.8_20140124_MJK firmware (4.2.1) - it was previously on the 0.6 firmware and had the same issue.
What I have experienced is that when connecting to a device with Bluetooth - in this case a Sony SW2, but have also tried Bluetooth headsets - it has problems pairing.
The phone sees the BT device as an available device, and when I select it, it starts the pairing process. Initially it seems to be ok and successfully pairs for 2-5 seconds, the the device is relisted as an available device, but not connected. I have had success twice. The first time was immediately after rooted my phone, and this was ok for several days, even rebooting my phone and the watch didn't seem to cause the issue again, but then it randomly stopped working. I was unable to connect until flashing with the 0.8 ROM. At this point is was again working for about 24 hours - even better than before - until I switched the watch off. Since then I have been unsuccessful in pairing again.
Interestingly, when I try to pair with my Galaxy Tab 2 I have the same problem, UNLESS I initiate the connection with the tablet, then it is fine.
I know that there were problems with the Bluetooth stack on 4.2.1 when it first came out, and it may be related to that, but can anyone offer suggestions as to what else I can try?
I've recently upgraded my ROM on my S2 i9100 phone from the standard 4.1.2 official to various unofficial ROMs. None of these allow me to use the hands-free features of the MKi9200 device. All of them will pair with the Parrot but the phone-book does not sync. Pressing the green button on the Parrot (which should allow you to voice dial) simply gives the message "phonebook is busy please wait".
I have reached out to Parrot without any joy to date even after 8 emails each way. My symptoms to them were along the following lines.
"1. The phone pairs with the MKi9200 still but still does not automatically connect when I get into the car.
2. After pairing the phone, the menu item “Bluetooth/paired phones” is still greyed out. It used to have my phone listed there before I upgraded. I guess that this is why the MKi does not automatically connect.
3. As noted above, I have to manually connect my phone now, whereas before I upgraded the smartphone Android version, it connected automatically. When it does connect, it says it is synchronising for a second or two.
4. I can dial a number using the “Phonebook” on the MKi device using the central knob and the menu system. I cannot use the green button as it always says the “phonebook is busy please wait”, even after 15 minutes.
5. When I finish a call, the iPod music does not restart automatically and I cannot start it manually using the “Play” button. The green play icon appears for a few seconds then goes away. I can play a track/playlist by selecting it from the menu system and the central knob.
6. I can play music from my iPod through the MKi9200 but when I press Pause, the red “pause” icon appears and the MKi “freezes”. I have to reboot the MKi to get it to work again.
7. I have tried various options for pairing the phone such as “force AT sync” but none have worked yet."
Any clues from anyone would be very welcome. I've had the Parrot for nearly 10 years and love it. I know it still o=works as I can pair an old phone (with my SIM card in it) and it works flawlessly. There is clearly something about unofficial ROMs that it doesn't like.
For info, I have always installed Micro GAPS or lower and have tried disabling bluetooth scanning and the software "Bluetooth File Transfer (Android)" by Medieval (versions 5.2 and the latest).
Parrot say the MKi9200 is not compatible with Android 8 but I have tried various other ROMs below that with no success.
Apologies if this post is in the wrong place but it seems to be an unofficial ROM thing to me. I feel there is something in these ROMs which is not compatible with my Parrot and was hoping someone would know what that was.
bluetooth has stopped since last software update LG-G5
i tried to clear cache, rest phone, remove and add the device.
nothing works, every time i try to connect the bluetooth in my car i got this message "bluetooth has stopped" and the bluetooth connection goes on and off.