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.
Related
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?
Hi Guys,
Always loved loading custom roms on my androids. Never had a problem I had to ask for help with until now. Please bear with me; I'm trying not to be noob-ish.
I'm running Resurrection Remix 4.4.2 on my Galaxy S2 GT-9100. I installed it last night. Had a big problem (after rebooting into recovery and then wipingdata/factory reset) - I couldn't mount my sdcard1 (externalSD) in CWMrecovery > hence I couldn't install the rom.zip from my SD card. I ended up using adb sideload to push the rom and GAPPS onto phone.
ROM working great so far, loving it! Suddenly; I can't adjust the audio slider for my main audio. The ring-volume and alarm volume can both be adjusted - and the speaker works when either of these two are used. My music/audio volume however won't lift up off zero. The speaker has the line through it to say it's muted completely.
I've tried using my hardware buttons, and the touchscreen to adjust it. I've searched Google & XDA. I've looking through all the settings on my phone. No luck. I've tried restarting phone. Can't think of any settings I've adjusted that could cause this. I was playing with contacts all afternoon, syncing FB images & organising Google contacts.
Please can somebody give me a hand - I've got my wedding coming up in 3 weeks and I don't have millions of hours to troubleshoot this alone.
Thanks in advance, let me know if there is anything I can do to help.
****This is strange. Just restarted my phone and it works again. Not sure then what is triggering the issue. Could be something to do with Open Mic for Google Now (it listens actively for "Ok Google"). Could be something to do with USB cable being plugged in and it thinks it is docked? Not sure any more. Working for now.****
****Now lost audio again! Was simply using my phone, using Google now to test the commands etc. Audio level dropped to zero, and I can't lift it up. Why! Perhaps it happened after phone went into standby?**** I've just checked and my WiFi doesn't go to sleep when phone is standby - it's already set to stay on.
For nearly a year we have not be able to upgrade our 1000+ Android devices operating with 4.1 Jellybean because the Bluetooth will not work properly. We recently discovered that this problem apparently began with Android version 4.2, coinciding with the change in the Bluetooth stack from BlueZ to Bluezoid. Here is the story: We use an Anoto digital pen with bluetooth and an app we developed, installed on an Android device (Kyocera Torque cell phone). After pairing the pen with the phone, individual transactions, written by the pen on paper are sent to the phone after a "send" box is checked. The phone then responds by activating its camera, pictures are taken then pen data and photos are sent to our server. This is the process which has been working flawlessly. The problem: After 4.1, the pen must be paired then the phone restarted. The "send" box must be checked twice before phone responds. After 8 sends, the process reverts to the correct process and remains until 20 total "sends" upon which the bluetooth function stops. The phone must be restarted. The pattern repeats. We have tested this on a variety of devices using Android 4.2 all the way to Marshmallow, all with the same results.
Please respond if you have some ideas which might help. We're hoping to find some work-around which does not require a major code re-write etc.
Hi,
I got my shiny S9+ two days ago and very happy with it although I have an issue with Android Auto.
My previous phone, Galaxy S7, never had a problem connecting to my car using Android Auto. It worked from the beginning and no issues whatsoever.
Now my S9+ refuses to connect with my car. Even manually launching Android Auto, the application still cannot register or recognize the car. The car also shows an error upon connecting the phone through USB (with or without Android Auto launched on the phone).
Just in case I tried three different USB C cables, uninstall/install Android Auto, clean cache & memory, reboot the phone, change the phone USB settings (MTA, File Transfer, etc), nothing seems to work. Somebody suggested me to use USB developer mode but I doubt it'll fix this issue.
I googled a little bit and found that Oreo 8.0 has issues with Android Auto that was fixed on 8.1. My phone currently has 8.0 so I wonder if somebody knows when Samsung will update their phones to Oreo 8.1
Thanks in advance,
Been using AA since day one without problems here.. And if someone suggested you try developer mode, why don't you just try it while you wait for 8.1?
Ok, thanks!
I have a PIoneer AVH4100-NEX and when I had my Nexus it was very flaky at best. I would have connection issues off and on frequent, but with my 9+ it has been flawless. Glad they worked it out.
jgirado said:
Hi,
I got my shiny S9+ two days ago and very happy with it although I have an issue with Android Auto.
My previous phone, Galaxy S7, never had a problem connecting to my car using Android Auto. It worked from the beginning and no issues whatsoever.
Now my S9+ refuses to connect with my car. Even manually launching Android Auto, the application still cannot register or recognize the car. The car also shows an error upon connecting the phone through USB (with or without Android Auto launched on the phone).
Just in case I tried three different USB C cables, uninstall/install Android Auto, clean cache & memory, reboot the phone, change the phone USB settings (MTA, File Transfer, etc), nothing seems to work. Somebody suggested me to use USB developer mode but I doubt it'll fix this issue.
I googled a little bit and found that Oreo 8.0 has issues with Android Auto that was fixed on 8.1. My phone currently has 8.0 so I wonder if somebody knows when Samsung will update their phones to Oreo 8.1
Thanks in advance,
Click to expand...
Click to collapse
If all fails, do the factory reset.
After S9+ got the update upon booting for the first time, the battery life was horrible. After the factory reset, however, happily ever after... (even though it was the pain in the a$$ to setup the phone again.
Thanks for all the tips. Although I delete my S7 profile in my car the solution was to perform a factory reset of my car's multimedia system/navigation. Now is working like a charm.
Javier
Anyone having problems with constant disconnects with android auto?
I have latest UK firmware installed along with the latest android auto and waze on my phone.
I can connect fine , sometimes I can drive 30 minutes without a disconnect, other times it is 5 minutes.
The only way I can get it working again is if I unplug the phone from the car and reconnect.
Then this happens again.
I have not made a journey yet where the phone has not disconnected at least once.
My old phone (nokia 8) never had this problem.
Im using a good quality USB cable.
Any ideas of which settings I need to change to help this issue?
Try using the phone manager app's battery settings to set Android Auto and Waze to manage manually as to me it seems that the battery management's the issue.
Sent from my Mate 20 Pro using Tapatalk
Works fine for me, using Waze/Spotify most of the time. Using default battery optimization for Android auto.
I'm using a Huawei cable.
You could try to the one coming with the phone to test.
Hi ,
Thanks for the replies.
Im using the cable that came with the phone in my car and it still has the same problem.
I changed the settings to manage manually, but again I plugged the phone in to my car and it stopped working after 5 minutes. I had to unplug and start again before the car would see the phone again.
There are 3 sets of settings in the manage manually option. did you change any of these?
Should say that im plugging into a vauxhall Astra 2017 car with the latest software installed on my car.
Thanks again for any help.
I've only had my UK Mate 20 Pro for about 3 weeks now, but I too am having issues with Android Auto. Initially I was getting disconnects, I think this was due to the handset trying to ask me how I wanted the USB connection to be treated - charge only, transfer files, MIDI device etc. It didn't seem to matter what I chose, it always flicked back to charge only. Or, it could have been down to the third party always-on-display app(s) that I was trialling and have since deleted.
The disconnects now seem to have stopped and it's more stable for me - I don't know why, it could due to the above deletions or a recent EMUI update (I'm on 9.0.0.210), or maybe Android Auto updated?
I now have different issues with AA, in that when I connect the handset and the Android Auto home screen comes up, there's no play button showing for my Audiobook app (Listen Audiobook Player), when I click into the app and click the play button it stays on 'getting your selection' forever and nothing plays. Incidentally I can start playing a book on my handset, but AA doesn't notice that anything's changed and stays on the 'getting your selection' screen.
The only way I have found to return functionality to normal is to restart the phone and enter my pass code - this takes me back to the phone desktop and a different error message which says 'android auto can't find any supported devices to use' (or something similar), when I unplug and re-plug all works as it should again - this is all a bit of a pain to do whilst driving, or requires me to park up.
Additionally I have noticed similar issues when switching audio apps i.e. to Spotify and then to an audiobook etc., It doesn't seem to go smoothly like it used to on my S8+
I'm using a 2017 Vauxhall Astra also ?
Ive sent a message to customer services to see if they can offer any help.
Dont know if we will have to wait for a firmware update to sort this out?
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
andywright1982 said:
Same every single time. Did a 120 mile trip today and had to disconnect and reconnect 7 times
Click to expand...
Click to collapse
Do an factory reset and try it again. See if it works.
Verstuurd vanaf mijn LYA-L29 met Tapatalk
Hi, Can you all please share the model of your car ? Maybe the issue is also connected to the car, not only the M20Pro. Thank you.
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
pau1777 said:
My car is a vauxhall astra.
I know it is not the car at fault as my last phone which was a Nokia 8 running android pie worked fine without any disconnections.
Click to expand...
Click to collapse
Same car. Used a samsung a9 yesterday and worked flawlessly.
Done a factory reset on the mate and still ****s up. If it wasnt such a good camera I would be getting a different phone
I tried it on a Mercedes CLS, just for a short run. It worked fine. With non-official Huawei Cable. Just basic USB-C. Maybe I need to try for a long run to be sure about it.
Anyone tried it on a Volvo XC40-60-90 ?
Disconnects
Did you find a solution to this? my device also suffers from constant disconnects and sets the USB method to charge only and as soon as you change it just goes straight back. battery management is set to manual and all apps and phone are up to date. using it on a Vauxhall insignia 66 plate with OEM cable.
Hey guys,
The problem seems to be with a nearly full battery.
When the battery is >=92% the connection of AA drops very often.
Is anyone here with EMUI 10 to test if it's more stable?
EDIT: I've missed that today is the launch of the beta so forget my question.
Edit2: some links for the same topic.
https://support.google.com/androidauto/thread/15209528?hl=en
https://www.android-hilfe.de/forum/android-auto.3315/android-auto-verbindungsprobleme-bei-akku-ladung-ueber-90.920529.html