Related
I have figured out a work-around for the auto pairing failure. I will give a step by step workaround how I did it. In my situation, I have a Mazda CX-5 and a Samsung Galaxy S3. But I am confident, that it will work with all Android 4.0.4 versions and other carkits, because the problem is most likely the same issue.
The reason why the phone won't auto pair, is because the phone does not give your carkit permission to download call history and other data. Even if you granted the phone this permission with the initial pairing.
If you have a carkit that supports multiple bluetooth profiles (multiple phones), like my Mazda CX-5 does, then you can also have your phonebook downloaded to your car. If your carkit supports multiple profiles, start with step 1. If yours doesn't, start with step 7. This guide is specifically for the Mazda CX-5, so some steps may be (slightly) different for your car model or make.
Here is the step by step guide:
1. Make sure you have no existing bluetooth pairs. Clear all pairs in your carkit and your phone.
2. Pair the phone with your carkit. You can see the randomly generated code on your phone and on the car display. Press ok to pair. (other carkits may need you to input "0000" or "1234", or maybe you have to input a code yourself)
3. Your phone will ask 2 questions about permissions. Check the box and allow. The phone will start to sync.
4. You carkit is done with syncing and it will ask you if you want to download your phonebook. Do this.
5. When its done copying, clear the Bluetooth pair on your phone (not on the Carkit!)
6. Give your phone a different Bluetooth name
7. In your carkit choose to pair a new phone (with the new name you just entered).
8. When the phone asks for permission for the carkit, check the box and choose cancel. Do this for both questions.
You don't have to copy your phonebook again (you can't anyway because you denied permission), but the phonebook that was downloaded earlier will still be available. Now the phone will pair automatically! With this trick you have your phonebook and automatic pairing.
I haven't seen what this does for media-audio streaming. I don't use that, but I can image that it doesn't work, because of the denied permissions.
There is another downside to this though (there always is, isn't it?). You cannot update your phonebook easily. If you want to update your phonebook, repeat the whole procedure.
I hope this will work for other people with different phones and cars too. At least this is a workaround until Google/Samsung comes with a fix. Please let us know if this works in your situation. To keep things structured, please use this format:
Car: Mazda CX-5
Phone: Samsung Galaxy S3
Works: Yes
That's OK !!
Car : Renault Scénic
Phone : Samsung Galaxy S3
Works : Yes, fine !! (with the MP3 reader too !...)
Good stuff!
Car: Vauxhall Vivaro van
Phone: Samsung Galaxy S3
Works: Yes, but can't get access to the phonebook as bluetooth keeps dropping out before it downloads. I don't really mind that though. At least I can now use my phone!
Man thanks for this fix!
DJ41 said:
I have figured out a work-around for the auto pairing failure. I will give a step by step workaround how I did it. In my situation, I have a Mazda CX-5 and a Samsung Galaxy S3. But I am confident, that it will work with all Android 4.0.4 versions and other carkits, because the problem is most likely the same issue.
The reason why the phone won't auto pair, is because the phone does not give your carkit permission to download call history and other data. Even if you granted the phone this permission with the initial pairing.
If you have a carkit that supports multiple bluetooth profiles (multiple phones), like my Mazda CX-5 does, then you can also have your phonebook downloaded to your car. If your carkit supports multiple profiles, start with step 1. If yours doesn't, start with step 7. This guide is specifically for the Mazda CX-5, so some steps may be (slightly) different for your car model or make.
Here is the step by step guide:
1. Make sure you have no existing bluetooth pairs. Clear all pairs in your carkit and your phone.
2. Pair the phone with your carkit. You can see the randomly generated code on your phone and on the car display. Press ok to pair. (other carkits may need you to input "0000" or "1234", or maybe you have to input a code yourself)
3. Your phone will ask 2 questions about permissions. Check the box and allow. The phone will start to sync.
4. You carkit is done with syncing and it will ask you if you want to download your phonebook. Do this.
5. When its done copying, clear the Bluetooth pair on your phone (not on the Carkit!)
6. Give your phone a different Bluetooth name
7. In your carkit choose to pair a new phone (with the new name you just entered).
8. When the phone asks for permission for the carkit, check the box and choose cancel. Do this for both questions.
You don't have to copy your phonebook again (you can't anyway because you denied permission), but the phonebook that was downloaded earlier will still be available. Now the phone will pair automatically! With this trick you have your phonebook and automatic pairing.
I haven't seen what this does for media-audio streaming. I don't use that, but I can image that it doesn't work, because of the denied permissions.
There is another downside to this though (there always is, isn't it?). You cannot update your phonebook easily. If you want to update your phonebook, repeat the whole procedure.
I hope this will work for other people with different phones and cars too. At least this is a workaround until Google/Samsung comes with a fix. Please let us know if this works in your situation. To keep things structured, please use this format:
Car: Mazda CX-5
Phone: Samsung Galaxy S3
Works: Yes
Click to expand...
Click to collapse
This does not work for my 2010 Altima, but glad to hear someone is able to fix their problem. Maybe I should go buy a Mazda :good:
POSSIBLE SOLOUTION
Guys, this problem was driving me nuts, just like many it worked the FIRST time it synced with my car but after that no go ! i randomly was trying stuff until something odd happened, i installed this program : https://play.google.com/store/apps/details?id=it.medieval.blueftp&hl=en and tried connecting to my car within the program, from now on, as long as that program is running, EVERYTHING is working, i can even get to my Text Messages from my car , all good !!! hope this helps you guys.
Running AOKP ROM on Rogers S III.
Cheers,
DJ41 said:
I have figured out a work-around for the auto pairing failure. I will give a step by step workaround how I did it. In my situation, I have a Mazda CX-5 and a Samsung Galaxy S3. But I am confident, that it will work with all Android 4.0.4 versions and other carkits, because the problem is most likely the same issue.
The reason why the phone won't auto pair, is because the phone does not give your carkit permission to download call history and other data. Even if you granted the phone this permission with the initial pairing.
If you have a carkit that supports multiple bluetooth profiles (multiple phones), like my Mazda CX-5 does, then you can also have your phonebook downloaded to your car. If your carkit supports multiple profiles, start with step 1. If yours doesn't, start with step 7. This guide is specifically for the Mazda CX-5, so some steps may be (slightly) different for your car model or make.
Here is the step by step guide:
1. Make sure you have no existing bluetooth pairs. Clear all pairs in your carkit and your phone.
2. Pair the phone with your carkit. You can see the randomly generated code on your phone and on the car display. Press ok to pair. (other carkits may need you to input "0000" or "1234", or maybe you have to input a code yourself)
3. Your phone will ask 2 questions about permissions. Check the box and allow. The phone will start to sync.
4. You carkit is done with syncing and it will ask you if you want to download your phonebook. Do this.
5. When its done copying, clear the Bluetooth pair on your phone (not on the Carkit!)
6. Give your phone a different Bluetooth name
7. In your carkit choose to pair a new phone (with the new name you just entered).
8. When the phone asks for permission for the carkit, check the box and choose cancel. Do this for both questions.
You don't have to copy your phonebook again (you can't anyway because you denied permission), but the phonebook that was downloaded earlier will still be available. Now the phone will pair automatically! With this trick you have your phonebook and automatic pairing.
I haven't seen what this does for media-audio streaming. I don't use that, but I can image that it doesn't work, because of the denied permissions.
There is another downside to this though (there always is, isn't it?). You cannot update your phonebook easily. If you want to update your phonebook, repeat the whole procedure.
I hope this will work for other people with different phones and cars too. At least this is a workaround until Google/Samsung comes with a fix. Please let us know if this works in your situation. To keep things structured, please use this format:
Car: Mazda CX-5
Phone: Samsung Galaxy S3
Works: Yes
Click to expand...
Click to collapse
Car: Honda Accord 2011
Phone: Samsung Galaxy S3
Works: NO
I have many problems with paring the S3 to different devices (headset, carkit, modem) Even connecting the S3 to my Galaxy Tab 7.7 reuslts in the S3 not being able to sent photo's to the Galaxy Tab 7.7 only when I fist sent a foto from the tablet to the S3 I can then sent form S3 to tablet. Also Wifidirect does not work. The software of my S3 is:
Android: 4.0.4
Baseband: i9300xxlfb
Kernel: 3.0.15-782020-user
Buildnummer: I9300XXBLFB
Any discussion with Samsung support and product managers did not resolve in a solution, they continously point the issue to the carkit, headset, modem supplier. Even the problem with connecting to the Samsung tablet is waved as "Differnt software, different hardware no guarantee that is compatible".
Solution
So I have reset the S3 back to factory settings which removes all apps not installed by me and all personal settings. Then I did following:
I installed, on the Samsung Galaxy S3 the first version of Samsung factory ROM (Build I9300XXALE8 for region Europe which is also 4.0.4 but the earlier version) using procedures and software(odin) to install custom roms. This does not void the warranty as the unit is not being rooted but only downgraded to an earlier official Samsung softeware
Then reset the S3 again to factory default settings.
Started the pairing with the Bluetooth device. They all started to pair and work correctly.
Removed all pairing profiles again form the phone and tried to pair again.. it kept doing the right thing.
Turned off the phone, turned on again and autopair with the carkit worked flawless. (my carkit is a Pioneer HD1BT). Same with headset and modem.
Install Samsung automatic software updates which upgrades the device ROM to newest version Build I9300XXBLFB. Manual disconnect and reconnect kept working
If one removes any BT connection profile on the phone after the software update, the BT connection/pairing problems with that device will come back and you need to do the whole procedure again
Bottomline conclusion: The latest Samsung updates has broken the ability to create a pairing profile with some bluetooth 2.0 devices.However, once the phone has Bluetooth connection profile for that the device, it keeps working.
The blame of Samsung towards carkit mfg's is incorrect. . It also has nothing to do with Bluetooth 4.0 compatibillity with 2.0 devices. (iPhone 4S, HTC One X are bluetooth 4.0 and the HTC One x is also Android 4.0.4). It is a pure Samsung sofware problem!
Either way It sucks. This is supposed to be the best phone on the market and its not without bugs
I received an OTA from Sprint and my bluetooth is now working as intended in my car. Have others received this OTA and had their bluetooth issues resolved?
I'm having a similar issue, but it only fails to autoconnect once I have set it to use the phone as a Bluetooth audio device.
Car : Volkswagen Golf (Rabbit) GTD
Phone : Samsung Galaxy S3
Works : Yes but can't sync contacts
All worked fine with LFB ROM (auto pairing and contacts sync) but from LG6 (LG8, LG9 and LH1) my phone disconnected 5sec after a contacts sync and auto reconnect 1min later...
So I just paired the phone without contacts synchronising.
Good news for everyone : everything works fine with JB (contacts, auto pairing...) !
Soon on Criskelo ROM :good:
Bluetooth woes
Erwan960 said:
Good news for everyone : everything works fine with JB (contacts, auto pairing...) !
Soon on Criskelo ROM :good:
Click to expand...
Click to collapse
Which JB Rom did you use?
mikeinstlouis said:
Which JB Rom did you use?
Click to expand...
Click to collapse
LH7 today but still problems in fact. I had a very lucky test... cause today it's impossible to synchronize contacts correctly without being disconnected every 10 secs.
All I can do is pairing S3 and car kit without contacts...
I think I found a solution that seems to work well for me. I tried 3 times and it works.
I tested one last time just leaving a blank LH7 stock ROM then a nandroid backup from a previous version and if it is confirmed, I will explain the process. :laugh:
I solved the problem! (at least with my config)
For those interested it's in french here : http://www.tmaddict.com/forum/viewtopic.php?f=218&t=25446&p=332863#p332863
If you need help to translate, just ask !
Robmtx said:
I received an OTA from Sprint and my bluetooth is now working as intended in my car. Have others received this OTA and had their bluetooth issues resolved?
Click to expand...
Click to collapse
I just installed the Tmobile OTA update and verify that the bluetooth reconnection issue has been resolved. I was using the workaround prior to this update and it worked as stated. After the update, I removed the pairing profile and re-pair from scratch and it worked right away. My issue now is that only a small portion of my (google) contact list gets transferred to the car. If anyone has any suggestions on workaround, it will be much appreciated
Stupid question but we never know... : did you wait long time enough ?
Check your google contacts and avoid :
- *
- non-ASCII characters
- email addresses with 'home' or 'work' attribute
With a little luck ...
Ive been trying to figure this out now for a month and so far i have found:
If i restore back to stock image (rooted) with samsung bloatware bluetooth will work perfectly fine.
If i then go to use TB to restore all my apps data etc, whenever i get into the car i will then get aprox 30 seconds - 2 minutes delay in the pairing.
If i restore back to stock and just use phone book it works perfectly fine. So i wondered if something was in the restore.
If i then flash a custom rom (any rom 4.0.4) on it will just take 30 mintues or whatever the timeout i have set in the bluetooth config file, this in theory is a dead end does nto work. If i then reflash the custom rom and do a complete user wipe, fix perm and nuke all the cache it then works perfectly fine with the custom rom (exactly like the stock).
I then can go to the car and it will pair perfectly. If i then go to TB and restore (including bt pairing etc) i get stuck in the 30 -2 minutes pairing, sometimes even longer.
Now here is the strange part, if i know my phone is at the stage where it will pair within 2 minutes i know i can restart my phone and it will pair instantly! If i turn off BT and turn it back on it will not pair.
OK so now i kind of know how to get it working but not as perfect as walking to the car and it pairs within a second or two. If i then flash a kernel (any i have tried about 4 of the popular ones) i then get 0 pairing, it can try for 10 minutes - 20 minutes it will just not pair. I then have to reflash over on top the custom rom with full bloatware.
Ok so now if i try the same as above minus the bloatware i get stuck in the non pairing mode again. non of this install bluetooth.apk, pressing cancel to contacts works for me. My BMW, AUDI will just get stuck in limbo where its paired but the connection is similar to a phone call for an unlimited lengeth of time it will just not work.
My current state of the phone is like this... OMEGA ROM (any version 4.0.4), stock kernel, FULL bloatware and my phone will pair either instantly or <2minutes. If it fails to do this a restart of the phone will pair it instantly.
I am able to freeze bloatware but any removal and the BT just hits deadlock. Now what is weird is i never ran my phone with bloatware at all up until all these problems started so something in the last month has sent my bt messy. even restoring back to my rom backup from when it was workign wil lnot fix it.
This is not a car BT issue as i have tried three cars and they work perfectly fine with any other phone.
I am getting kind of sick of sitting in the car flashing roms, trying things etc. I do not know what the problem is but atleast 2mins waiting time is better than not having anything
I'm on JB (Revolution HD 12.2) and my S3 still won't pair with a car kit, no matter what I do. :\
I have a Galaxy S3 I9300 for a couple of weeks now and I love it, other than the fact that I keep having a strange issue with the Bluetooth connection with my carkit. I've been searching forums for similar issues and I found a variety of carkit related problems, but none of the ones I found describe the same problem as what I'm having:
- Initially the Bluetooth connection works fine and I can play music or make a call through the carkit just fine
- When I switch off the car's systems and don't use any apps on the phone in the meanwhile, and then start the car's systems again, it establishes the Bluetooth connection just fine again
- When I switch off the car's systems and I use other apps for a while and then start the car again, it won't work. Bluetooth does appear to connect, but after that it just doesn't play ball. When I try to play a song at this point, the phone shows the song is playing, but neither the phone nor the car audio produces any sound
So anyway, every morning before leaving to work and every evening before going home, I reboot my phone first. Then I step into the car and it establishes the Bluetooth connection just fine. But if I don't reboot the phone first, it just won't work. Now I guess I could setup a tasker profile to automatically reboot the phone, but I'd rather just get the problem fixed.
I run a Galaxy S3 I9300 with stock Android 4.1.1, rooted. I have already tried to run the "Bluetooth Fix Repair" app and afterwards had to pair the phone with the carkit again, but that made no difference.
Any help would be greatly appreciated!
*bump*
Some additional info:
This issue has now also happened a few times while driving. While music (through Spotify) was playing over the bluetooth carkit, it would sometimes just stop working when I opened a different app (like for example opening an SMS). Spotify was still running (and the song was still ongoing) and also the bluetooth connection still showed as being connected, but it just wouldn't produce any sound anymore.
Anyway, it seems clear to me that this is a bluetooth issue, but I have no idea how I can troubleshoot this beyond what I've already done.
I would be happy to pay whoever can fix this problem..
With an issue like you are describing it may be helpful to list the headunit model too. I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
ItzCrooK2UxD said:
With an issue like you are describing it may be helpful to list the headunit model too.
Click to expand...
Click to collapse
My car is a Renault Megane RS, the carkit was built in. I believe it's called Renault Carminat TomTom.
ItzCrooK2UxD said:
I do not own an S3 but I have a multimedia headunit (Pioneer AVH P4400BH) and have found that toggling my Bluetooth on and off will help the headunit to see the Bluetooth on my Android device. This may not resolve your issue though.
Click to expand...
Click to collapse
I've covered everything like that in about 100 different ways, none of which made any difference.
ItzCrooK2UxD said:
Another thing to consider, your headunit may have an update-able firmware. That said if your headunit does have an update-able firmware I would check out the procedure, ensure there is a way to roll back to your current firmware and try that. If your headunit was purchased at an electronics or and audio retailer you may wish to speak with them. Your issue may not be with your phone but with your headunit, but this should help as far as troubleshooting since your issue involves multiple devices.
Click to expand...
Click to collapse
Good point. It does have an SD card slot, but as far as I know that's only to update the maps of the navigation system. I'll see if I can figure that out.
Thanks for the tips!
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Apoc_ said:
By the way - I do think that it's unlikely that the carkit itself is the troublemaker. Especially because opening an SMS on my phone can trigger the whole thing to stop working (it doesn't happen every time, but it did happen several times). Please correct me if I'm wrong.
Click to expand...
Click to collapse
It is in fact very possible that it is your phone, but wanted to throw it out there that bluetooth headunits can be troublesome on their own. Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me. Also do you have other bluetooth devices in the car, such as the 3GS you mentioned?
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
ItzCrooK2UxD said:
Now I am not familiar with your headunit, but does it save bluetooth IDs? Like on my headunit and many other aftermarket headunits, it will save 3 bluetooth devices. If it does, have you tried clearing other devices and moving your S3 to the top? Odd as it sounds this has made a difference for me.
Click to expand...
Click to collapse
Yeah I had read that too in some other thread (I went through just about every bluetooth related thread I could find, before I posted this topic). Mine saves up to 5. It didn't have anything in there except for my previous phone, which I had cleared. I also tried re-pairing the S3 several times, that didn't make any difference either.
Now, I just read somewhere that some people are having disconnection issues on the same carkit. In their case, in the end the problem turned out to be that their carkit will import all of their contacts from their phone (so you can call people even while your phone is in your pocket), and this would cause trouble when there are contacts without a phone number associated with it (just like my thousands of Exchange contacts). The people in question are talking about random disconnects though, whereas in my case it happens after doing some stuff on my phone. So it's probably unrelated, but I'll give that a try anyway just to rule it out. I just need to figure out a way to stop the carkit from importing contacts, because removing thousands of email contacts is obviously not an option.
I'll keep this topic updated with any progress. If anyone has any other ideas, please keep em coming. Thanks for the help so far!
ItzCrooK2UxD said:
Also a logcat of this happening would be beneficial. If you do not know how to pull a logcat there is an app on the market called catlog or alogcat. Both are free and are invaluable in troubleshooting a ROM issue. In short it tells a developer what is going on as far as events being triggered or failures within the ROM.
Click to expand...
Click to collapse
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Apoc_ said:
Didn't think of that, great tip, thank you! I do run the stock ROM by the way.
I've installed alogcat just now. Does it just keep running automatically in the background?
Click to expand...
Click to collapse
It reads a file that is being constantly updated (which happens to be the logcat file). Typically I will clear it right before doing what it took to cause the failure, like in your case in your car with the bluetooth on.
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
YoghurtPL said:
I've got Audi with BT and S3 with custom rom and I've got similar problems with BT. It connects automatically but if I switch off BT in phone and switch it on again - it doesn't connect any more. I had this since I bought a phone and it was on all ROMs I used.
Click to expand...
Click to collapse
Yep - I have that too. The weird thing is that in that situation the phone does seem to think it is connected, while it really isn't. Just to be clear: this is not the only way to cause this issue (because it also happens when trying to reconnect the Bluetooth while on the phone it hasn't been disabled in the meanwhile).
So far I haven't been able to pull anything related from the logcat.
Also, while reading up on common bluetooth issues, I came across some posts of people who were saying that some phone/carkit combinations are having trouble with 2-way communication (because I can stream music from the phone to the carkit, but I can also change a song using the carkit or initiate a phonecall from the carkit). I'm going to try to only use communication initiated from the phone, and see whether that makes any difference. In the meanwhile: does anyone happen to know anything about 2-way communication issues with bluetooth, and how to overcome such issues?
Update:
- Updated carkit to latest firmware. No change, still same problem
- Have not been able to capture anything unusual in the logs
- I have a Bose Soundlink now, which is a wireless speaker. Whenever my S3 is connected to the Soundlink (with bluetooth), wifi doesn't work. Upon turning off bluetooth, wifi instantly works fine again. So this definitely confirms this is a problem with bluetooth on the phone, not on the carkit.
- Wanted to upgrade to Android 4.1.2 but Samsung won't let me, as it says the device is modified (rooted). Triangle away isn't helping. Damn you, Samsung. This is *the* reason I moved away from Apple, as I don't like companies who don't let you use your stuff any way you like. And now Samsung is moving down the same route. Idiots. Anyway, I guess the only option left, is to start using a custom ROM.
Does anyone happen to have experience in terms of solving bluetooth problems by using a custom ROM? I'm thinking of using Cyanogenmod 10.1
In the meanwhile I have upgraded to Android 4.1.2: still the same problem.
I have also discussed this matter with quite a few other Samsung smartphone owners, and all of them appear to be having the same issue. Most of them just don't seem to be bothered to spend time on looking for a fix.
Also, I have figured out that this problem is specific to media streaming. I'm able to use my phone on the carkit for calls at any time, without having to reboot first. Only when I try to listen to music, the problem occurs.
Anyway, I have ruled out that this problem is specific to me or my devices - this appears to be a global issue. So I'm completely puzzled as to why there's not a lot more fuss going on about this.
If anyone has any more suggestions for a resolution of this problem, please share.
S3 bluetooth connection problem
Had the same problem with my S3 and renault megane III handsfree bluetooth system.(Arkamsys software version 2.2.0.19 auditorium)
I downgraded to 4.0.4 baseband I9300CELH1 (stock) and problem seems fixed
hope this helps.
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Carkit bluetooth issue
Apoc_ said:
Hi Bennes,
Thank you for your response.
I'm still dealing with this problem myself. All upgrades so far haven't made a difference. So far, I've been able to figure out that if I first initiate a phonecall, after hanging up, the audio streaming works (while before the phonecall it usually wouldn't). This works about 8 out of 10 times (the other 2 times it doesn't make a bluetooth connection at all). So what I've done, is to use Tasker and to automatically make it call my own phone number whenever bluetooth gets connected to the carkit, and hanging up after 3 seconds. But this is obviously far from ideal.
Do you know whether it is possible to change the baseband version without changing the firmware version? I wouldn't like to downgrade to an older firmware version, as I like the new features in the newer versions. I do also prefer to stick with the stock firmware, but that's not a requirement.
Click to expand...
Click to collapse
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Bennes18 said:
mmm, don`t know about baseband only. Try google.
I have read that after downgrade to 4.0.4 and then upgrade again to latest stock version, bluetooth connection keeps working.
I cannot confirm this as i am still on 4.0.4, but will get an update of the arkamsys radio to the latest renault firmware version next week and then start experimenting again. i will report back once i have new results
Click to expand...
Click to collapse
BB only, try this :
http://forum.xda-developers.com/showthread.php?t=2106424
Confirmed the update thing, i have updated the S3 to version 4.1.2 BB I9300CEELL1 and have no bluetooth issue whatsoever, car audio still on 2.2.0.19 byt the way
Pretty strange ... , but glad its working !
I have the same issue with a Ford Focus =/
also, while using CM or Omega, the music title never changes.
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
i had a similar problem but with my car's bluetooth. i cleared up my contact listed and the problem was resolved.
here is where i found the solution: http://forum.xda-developers.com/showthread.php?t=2646592&page=2
hope you come right.
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
...
onurcandan said:
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
Click to expand...
Click to collapse
I did not find a solution yet! You yeah?
Jackal107 said:
I did not find a solution yet! You yeah?
Click to expand...
Click to collapse
I have the same issue with my headset. Hope someone will find a solution soon.
I too have same problem!!
Whats wrong with samsung!!, sometime Wifi problem and sometime bluetooth.:silly::silly:
earlier I was on 4.1.2 and it was working good with my jabra clipper bluetooth headset, after updating to 4.4.2 it sucks!.
according to my observation,
The OS is trying to save battery by limiting the bluetooth signal strength!, and the same problem with wifi also.:silly:
Looking for a workaround. If i find any will post for sure.
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Click to expand...
Click to collapse
Yepp, I know that threat. But on my N7100 nothing works. In the meantime I'm on Paranoid ROM with 4.4.4 and it's a little better, but not much.
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Click to expand...
Click to collapse
Hi
and have the same problem with the bluetooth, the phone in my pocket, Samsung headphones on the head and lose the music signal, conclusion .... android version
Before to upgrade I had 4.3 and works very well and now I upgraded to 4.4.2 my Note 2 with Phantom_V7.0 and work awesome but has a minus....... the bluetooth signal gets lost and it's not about the power,for ex i have battery with 4200 mAh
I will continue to keep looking this problem and I will return
There is no way to get better connection. The only way is using a 4.3 ROM
Seems like the problem is solved.
Hey guys!
It seems to me I’ve found the solution!
But firstly, a few words about the problems I’ve got…
I have Samsung Galaxy Note 2 and, when I decided to replace my old Plantronics Discovery 975 with their Voyager Edge, it had installed Android 4.3.
Both events, start using the new Bluetooth devise and upgrading to KitKat (4.4.2) occurred almost simultaneously, so it was pretty difficult to recognize what was the source of the problems that I run into – hardware/firmware issues of Voyager Edge or KitKat’s quirks. The problems were the following:
- Poor Bluetooth connection that resulted in distorted sound (not always, but often) thru the headset.
- Regularly losing the ability to use various Edge’s features, such as calling back to the last number, checking the battery status, recognizing who's calling, etc.
- Note’s battery drained badly – instead of 50-60% left at the end of the day, I got 10%...
I spoke several times with Plantronics support, but they ended advising me to replace the headset. I have neither found the specific solution in the internet and it was even reported that the factory reset would hardly help. So, that was almost the dead-end. But there was one pretty weird solution that helped to some people – deleting the duplicates in the phone’s contact list. But, since I had NO duplicates, it didn’t seem to be helpful. But then, I noticed one very strange detail – during the moments when Edge worked properly it correctly pronounced the names from my phone book, even tho some of them were quite unusual for English speaking "robot". All of them, but one – my mother’s record, which was a simple “Mom”, but when she called me, the Edge’s notification was definitely not “calling from mom”…
So, I just renamed “mom” to “mother”!
Guys, can you believe that, but ALL the problems (both phone’s and headset’s) have just gone! I’ve been using it for almost a week already and it’s OK. So, you may check your contact list, whether it sounds correctly.
Well, one issue left – weird/funny bug of the Edge’s firmware – start playing music when you take it off the cradle. (2 latest firmware updates didn’t cure that…). I just long press the voice button on the Edge to pause it. Not a big deal, to be honest.
Oh, just one last note – since Voyager Edge cannot be rebooted you can do the following if/when you neither hear the music (!), nor the report that the headset is connected when you take it off the cradle. Just long press the Call button on the headset (in my case it runs Note’s S-voice) and then everything works just fine. (Checked twice.)
Hope that this will help you too.
Cheers,
Max
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
harvey186 said:
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
Click to expand...
Click to collapse
Hi Harvey,
Absolutely the same reaction was mine, when I read the comment by dawolverune (see page 1 of this thread). How deleting duplicate contacts might help…
Well, if assume that I tell the truth (and I actually do! ), then the solution may be explained in 2 ways: a) logical – I’ve been hammering with all this stuff for almost a week and nothing helped until I renamed that single contact and then, it just start working and b) technical – since Voyager Edge pronounced the wrong name it means that it took it from somewhere, but definitely from the wrong place and this might require extra “efforts” from the Bluetooth receiver/transmitter, etc. This indeed may result in abnormal behavior of the devise and “eating” the battery. If re-phrase the title of S. Coppola’s movie – here we had “Lost in Bluetooth” case.
Cheers,
Max
hack fix
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
ivan_109 said:
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
Click to expand...
Click to collapse
cool, it seems, that this hack is working
Thx
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
I have the Exact Problem, and no one seems to have a solution to this. Did u find any by any chance ??
Thanks
SOLUTION OF BLUETOOTH DROPPING after 4.4.2 update
Yo !
I found the solution. No one has to downgrade Note 2 (N7100) to Jelly-bean in order to fix the Bluetooth range and WiFi dropping issue.
The fault is with the latest update from Samsung itself, May be it is a tactic to make people shift to the newer phones.(who knows) !
Anyway the solution to this problem is to Flash it with Odin it a previous release of 4.4.2.
In my case which is from the INU (India) region the release of August that is 29.08.2014 is a faulty update.
So i downloaded the older one and flashed it.. then everything worked perfectly as if the phone was new
Here is how to do it:- [BACKUP YOUR PHONE WITH KIES 3]
1. Check your version from *#1234#, Compare the version with Near August version of your Region. If it is same you better change it to get a way better performance.
2. Look up the earlier ROM version released from samsung-updated .com , http://samsung-updates.com/device/?id=GT-N7100&details=Galaxy_Note_2__International , I personally flashed it with the first version of Kit-Kat that came for note 2 in INU region. on the 8th April (08.04.2014).
3. Download ODIN http://www.mediafire.com/download/mbvtjub21ehsxrl/Note+2+Odin.zip
4. Install Samsung USB drivers http://www.mediafire.com/download/9qaqkld45387lzi/Skyrocket_GSII_ADB_Drivers.zip
[IF THE LINKS DON'T WORK then GOOGLE THEM AND INSTALL]
5. Power off your Samsung Note 2.
6. Hold Volume Down, Power, and Home Buttons at the same time. You will enter the ODIN DOWNLOAD MODE on your phone.
7. Press Volume up to Continue. It will Show "Downloading" "do not power off"
8. Connect your device to the PC where you have put ODIN and the md5 file (Firmware you want to flash with)
9. It will show connected to your device name on the top left of ODIN which means that it recognizes your device.
Click on PDA and select the firmware that u downloaded to flash Note 2 with.
It will lag for a few seconds but let it take its time.
When it is done. [Refer Image attached]
10. Press Start [It will take around 5 minutes, 3 minutes give or take]
11. It will Automatically Reboot your phone. Do not disconnect the USB cable.
After the boot is Complete ODIN will show a PASS on the left Side. Which means that the Flashing Process has been a Success.
If it shows fail then Repeat the process from STEP 6 all the way till STEP 11.
{ RECOVERY STEPS:- this will wipe all your data}
[Also, If device is Stuck at setup connection or on any other process, then disconnect your Note 2 from PC, close Odin, remove phone’s battery and put it back inside AFTER 5 seconds, press Volume up, Home key and Power key at the same time, When the Logo comes then Leave the Power button but keep pressing the other 2. Wait for it to show MANUAL MODE. Select Wide Data and Factory reset with Volume down and press power to continue, Then again wipe Cache.
Select Reboot . Now it should work perfectly.
CAUTION :- DO THIS AT UR OWN RISK.
Is this problem appears in official update? Want to update, but dont want any probs)
Yes the problem is with the official update. Better not update it till there is another update of it available.
I'm thinking this might have to do with Samsung dropping the Bluetooth version from 4.0 back to 2.0. I have no idea why they would do that but I've been wondering why my phone listed version 2.0 when the specs for this phone always said version 4.0. As you can see my debug screen shows it as version 2 and not 4.0. My Edge shows 4.0 on that same screen. I can't recall if older builds for the Note 2 had 4.0 listed but I believe they did and kitkat lowered it. Guess that's their trick to get people to upgrade, break things on our phones quietly...
Sent from my SM-N915P using XDA Free mobile app
I can no longer activate the bluetooth of the watch. Strangely, it is still connected to the phone and everything works, but I can no longer connect my headphones and my cardio belt. Has anyone come across this problem before. is there a solution ?
Merci
Firmware update 4.2.3.0 don't change anything
https://youtu.be/TEBFZi0FCMM
Same problem. I can't pair phone with watch when I want using unlocking phone with Bluetooth.
Same problem, when I try to activate Bluetooth to pair it with my earphones, it says "Activating Bluetooth" and then "Bluetooth deactivated"
Same problem here. Can't pair with heart rate sensor (4.2.4.0 version). I send a mail to Amazfit, awaiting reply,
Same here, please see https://forum.xda-developers.com/smartwatch/amazfit/amazfit-stratos-3-bluetooth-earphones-t4052503
Anyone knows how to fix this?
It seems new update 4.2.5.0 fixed this, i had to turn WiFI first (earlier nothing worked).
k4hR said:
It seems new update 4.2.5.0 fixed this, i had to turn WiFI first (earlier nothing worked).
Click to expand...
Click to collapse
Can you please explain the steps? I'm unable to turn on wifi and therefore update the watch..
Hey,
i installed new update then tried to turn BT to check if it works now and it resulted in usual BT OFF, then i went to WiFi section, found my home network (had to type password in app) then i went back to bluetooth option and i was able to turn it on- i could find my HR belt in settings/accesories section of an activity.
edit, 02.04.2020:
today same problem as before- bluetooth keeps turning off
k4hR said:
Hey,
i installed new update then tried to turn BT to check if it works now and it resulted in usual BT OFF, then i went to WiFi section, found my home network (had to type password in app) then i went back to bluetooth option and i was able to turn it on- i could find my HR belt in settings/accesories section of an activity.
edit, 02.04.2020:
today same problem as before- bluetooth keeps turning off
Click to expand...
Click to collapse
Hi,
Can you try these steps?
Go to system Settings in the smartwatch.
Under Settings, scroll down list and tap "About."
Under "About," scroll down to "Legal Statement."
Continuously tap on "Legal Statement" until "Lab" appears below it.
Tap on "Lab" and select "Signal Strength."
Tap "Start." A Pass or Fail message will appear once the test is complete.
leugim1 said:
Hi,
Can you try these steps?
Go to system Settings in the smartwatch.
Under Settings, scroll down list and tap "About."
Under "About," scroll down to "Legal Statement."
Continuously tap on "Legal Statement" until "Lab" appears below it.
Tap on "Lab" and select "Signal Strength."
Tap "Start." A Pass or Fail message will appear once the test is complete.
Click to expand...
Click to collapse
I've just done the test and it passed OK.
However, enabling Wifi does not change Bluetooth behavior (still changes back to Disconnected)
theopulus said:
I've just done the test and it passed OK.
However, enabling Wifi does not change Bluetooth behavior (still changes back to Disconnected)
Click to expand...
Click to collapse
Mine has a different problem. When I run the test I get "Please retry".. you might have better chances that I do..
leugim1 said:
Hi,
Can you try these steps?
Go to system Settings in the smartwatch.
Under Settings, scroll down list and tap "About."
Under "About," scroll down to "Legal Statement."
Continuously tap on "Legal Statement" until "Lab" appears below it.
Tap on "Lab" and select "Signal Strength."
Tap "Start." A Pass or Fail message will appear once the test is complete.
Click to expand...
Click to collapse
I've tried the wifi connection trick, and it doesn't work.
Also, did the lab signal Strength test, and it says Fail. But I am able to connect to wifi, and to pair with the phone.
toffen said:
I've tried the wifi connection trick, and it doesn't work.
Also, did the lab signal Strength test, and it says Fail. But I am able to connect to wifi, and to pair with the phone.
Click to expand...
Click to collapse
It seems we are experiencing similar and related issues. Mine connects to the phone (using Bluetooth) but Bluetooth doesn't turn on (for earphones, etc.) and my wifi doesn't capture any network.
Already tried to factory reset several times and anything I can think of. Any suggestion is welcomed to try to fix this.
I will contact the Amazfit support again
leugim1 said:
It seems we are experiencing similar and related issues. Mine connects to the phone (using Bluetooth) but Bluetooth doesn't turn on (for earphones, etc.) and my wifi doesn't capture any network.
Already tried to factory reset several times and anything I can think of. Any suggestion is welcomed to try to fix this.
I will contact the Amazfit support again
Click to expand...
Click to collapse
Just to clarify, although the strength test fails for wifi, I am able to connect to a wifi using setting > connection > wifi.
Looking forward to see what they say to do. They told that I should contact my retailer to claim the warranty.
Any Updates
Any Updates
toffen said:
Any Updates
Click to expand...
Click to collapse
Not really.. The Amazfit support is not helpful.
I have installed the newest firmware using the instrucions on this forum but didn't fix it.
Found several people with the same issue in the forum but no fix..
Both bluetooth and wifi are not working for me. But I am able to connect to the app.
Hello, i have the same problem, see below the amazfit support answer
Hello There ，
How is everything going?
We have checked the log and sorry to tell your watch issue cannot be fixed online. Could you please kindly contact the seller directly to find a solution based on their warranty policy? If they need you to provide any evidence of the specific problems with your device, please let us know. We are more than happy to help! We appreciate your understanding and support!
I must send the watch to my seller to repair it.
thanks
Just to let You know, again new update 4.2.7.0 fixed issue for me, i can pair BT speaker and HR belt... Hope it lasts longer this time...
k4hR said:
Just to let You know, again new update 4.2.7.0 fixed issue for me, i can pair BT speaker and HR belt... Hope it lasts longer this time...
Click to expand...
Click to collapse
I am still on 4.2.6.0, when did you update?
Hi everyone,
I can't make any calls through a bluetooth connected device, on my P20 Lite ANE-LX1. I've tried connecting to a car FM adapter and with my Xiaomi Mi TW Lite earbuds.
Symptoms are:
- devices successfully pair with P20L
- devices successfully conneted, with connection sound issued from the devices
- devices set to enable on calls and music
- devices play music with no problem
- I can chitchat with google assistant through the devices
- when I make a call google assistant uses the paired device to announce "callin person xxxx", there is no calling tone, can't hear or be heard.
Steps taken:
- devices tested with other phones, no problem there
- checked sound volume in calls
- restarted devices multiple times
- disconnected and reconnected devices
- tried every combination of calls/music/contact sharing on BT device properties
- deleted devices, re-paired and re-connected devices
- cache and data deleted for bluetooth backgound process
- reset network connections
- after reseting network, did all the above, several times
- wiped system cache/dalvik
- searched this forum, sorry if I'm missing the answer, I HONESTLY tried to find one
- boot into safe mode, no joy for bluetooth calls
- downgraded with HiSuite, updated, paired devices before restoring apps, no luck
- did most of the above again
- disabled google assistant
I've been searching everywhere for a solution and got nowhere. I think I'm down to either factory restore, which I don't think will solve the issue as I already downgraded, or maybe this could be permission related in the scense that another app could be taking controll over BT. I've been looking at permissions, but can't make an educated guess.
I've been seriously considering risking bricking my phone to unlock the bootloader and flash a different OS as I've only flashed an Android once, 10 years ago (and it was easy back then).
Please advise!
Clear system cache
And this... toggle it on.
blackhawk said:
Clear system cache
And this... toggle it on.
Click to expand...
Click to collapse
@blackhawk Thanks for the quick reply.
I forgot to mention I already tried wiping cache/dalvik, added to the original post.
As for disabling A2DP I can't find it on my developer options (Android 9/MIUI 9.1.0.381). I'll try to find why and if there's an alternative way to do the switching.
Will wipe cahe/dalvik again, should I find a way to deactivate A2DP.
Android shouldn't be this complicated
SardaoVoador said:
@blackhawk Thanks for the quick reply.
I forgot to mention I already tried wiping cache/dalvik, added to the original post.
As for disabling A2DP I can't find it on my developer options (Android 9/MIUI 9.1.0.381). I'll try to find why and if there's an alternative way to do the switching.
Will wipe cahe/dalvik again, should I find a way to deactivate A2DP.
Android shouldn't be this complicated
Click to expand...
Click to collapse
That's odd. I don't know if that's normal or not for that device.
Androids can be quit the terror sometimes.
BUMP
Hey everyone, sorry for pushing, any other ideas?
Try bluetooth settings, advanced. See what options you have there.
Hi @blackhawk, no such option. Any advanced options are those accessed via developer settings.
Thanks for replying