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. :\
Related
Hi @ all,
since a few days i am a proudly HTC Hero owner. Its quite an amazing phone with many features and a steady growing Market.
At the weekend i tried to couple my Hero with my bluetooth handsfree set installed in my car. But what i recognized wasn't so much pleasing: The Hero didn't display the handsfree set in the list of available bluetooth devices.
Before i got the Hero i had a HTC TyTN II aka Kaiser and it worked well with the handsfree set.
Perhaps anybody else have some similar trouble or experience with this and maybe a solution, fortunately. It would be great to keep usage of my handsfree set furthermore.
Thank you and best regards
On handsfree there are some buttons right ? You need to press them in a combination so the handsfree can be detected by your Hero. Just search on the handsfree guide or internet. I cannot help you because I don't have it and don't know the button combination. When you find it go to settings and turn on Bluetooth on your phone. Just search it and connect to it
Hi omokas,
yes, you are right.. but i've done this.
The users guide says you have to press the main button for 1 second. After that you will get a feedback sound and the led gets flashing... so far so good.. everything is fine but the Hero doesn't recognize.
Hopefully there are no different bluetooth protocols or whatever the devices can't communicate.
Have you tried an application from Market ? It may to the job
But if not then your handsfree must be an older version that your Hero can't recognise. Before buying a new one make sure your phone works with other handsfrees.
Have you tried an application from Market ? It may to the job
Click to expand...
Click to collapse
No, i haven't tried yet. Can you recommend one?
At the moment i'm not able to try an other handsfree. But i've just seen the handsfree is able to store seven pairings... maybe there is the problem.
So i'm going to delete all pairings and give a next try.
Thanks
Yes try that. You could try the application "Bluetooth+Headphones".
Sorry if I am not able to help further but I don't use handsfree because I am 13 and I don't know how to drive.
No Problem... I am appreciate for any Help!
Did you get any results yet? E.g. did the removal of the other pairings work? Or the app from the market?
I'm quite interested in this since I'm still looking into getting the CK-100 build in my car
I am planning on getting that carkit wired up outside of the car, so I can at least give it a try and see if it wants to work. But don't have that much time to give it a try yet, end of next week perhaps...
I have a CK-7W and it works with my Hero (official orange ROM).
It was a bit of a nightmare to get paired in the 1st place, the hero failed to find it but I kept trying and it eventually found it. I think I might have reset the hands free though (pull the power for a few minutes).
The device usually pairs pretty fast, sometimes it takes a min or two but not often.
My only gripes are :
1: some times it doesn't send the audio to the speaker keeping it on phone requiring you to use a menu option to do so.
2: The ring tone isn't the one set on the phone but a generic ringer.
3: Occasionally the phone doesn't disconnect properly when the other end hangs up requiring you to do so manually.
I have a CK-15W car kit
and its fully supported
it even downloads the phonebook very well
ck7w and hero
My hero worked first time! To pair you need to leave ignition off and hold the button in until it beeps, not just a short push as that just turns the car kit on. Once its beeped search for it and then pair using code. As yet I have had none of the problems mentioned here. I hope this helps
I have the same phone (Android 1.5 stock ROM) and the same Nokia CK-7W handsfree set.
For me this works fine. Didn't have to press the button on the handsfree set. Just searched for BT devices and paired.
Hey guys, I upgraded to the Atrix from my Tilt2... I set up the bluetooth with my car (Audi A5) and the calling works fine but the car no loner imports my SIM contacts, recent calls, missed calls, and dialed calls list that my Tilt2 used to send over. Those options on the car are now just blank. Is there anyway to enable this? The bluetooth profile on both phones is just listed as "hands free". Is there any way to fix this or enable other connection profiles to send that data like my last phone did?
Thanks guys
I can pair my Atrix is my BMW 3-series but when it tries to download the phone book the BT connection drops. Sometimes I can start to make a call but it will drop the connection.
I can connect all my BB's and my HTC Inspire 4G just fine.
I think there is something wrong with the BT stack.
Ziuck said:
I can pair my Atrix is my BMW 3-series but when it tries to download the phone book the BT connection drops. Sometimes I can start to make a call but it will drop the connection.
I can connect all my BB's and my HTC Inspire 4G just fine.
I think there is something wrong with the BT stack.
Click to expand...
Click to collapse
I think you may be right... I did some more online searching after the post and stumbled upon an Audi forum where multiple people have lost the ability on several different car models after moving to a stock android device... however, it appears things fix themselves with CM roms which may have a more sophisticated BT stack. I wonder if it's hopeless about having that capability until 2.3 or the bootloader is cracked?
If I can't get this fixed soon then I will be forced to return this phone.
How can they screw up something so simple??
UTZorro said:
Hey guys, I upgraded to the Atrix from my Tilt2... I set up the bluetooth with my car (Audi A5) and the calling works fine but the car no loner imports my SIM contacts, recent calls, missed calls, and dialed calls list that my Tilt2 used to send over. Those options on the car are now just blank. Is there anyway to enable this? The bluetooth profile on both phones is just listed as "hands free". Is there any way to fix this or enable other connection profiles to send that data like my last phone did?
Thanks guys
Click to expand...
Click to collapse
I have this same problem in my Chevy Volt. Sometimes the phonebook works (but very slowly) but the call lists never work. Also seems to take a very long time to pair initially.
Sent from my MB860 using XDA App
A lot of cars can only import the phone book from the SIM card. Not from any other application on the phone.
So if your phone book is in Google Contacts or some other application...you'll need to port it into the SIM card itself for most cars to be able to read it.
Return it. I have new A4 and atrix pairs fine. I actually think its the clearest device I've used in my car yet
Sent from my MB860 using XDA App
fade?
"I have new A4 and atrix pairs fine."
And do you know WHICH phone book your numbers are in, or which phone books the A4 can pair with?
If his BT is connecting, and the phone is working over BT, there's no reason to think the phone is defective. yet.
UTZorro said:
I think you may be right... I did some more online searching after the post and stumbled upon an Audi forum where multiple people have lost the ability on several different car models after moving to a stock android device... however, it appears things fix themselves with CM roms which may have a more sophisticated BT stack. I wonder if it's hopeless about having that capability until 2.3 or the bootloader is cracked?
Click to expand...
Click to collapse
It's not a BT Stack problem...it's an Audi problem (or BMW, etc...). The manufacturers need to program their devices for Android. The ability to grab contacts and such isn't a standard bluetooth handsfree device option. It has to do something extra. How it *handles* that extra something differs by device...which is why some don't work with Android devices.
On top of that, there's a dialogue when you first pair the device that asks if it should have access to your contacts, call lists, etc...that you have to "Allow" or it won't ever be able to get those lists. It's been the same way on every Android phone I've ever used. If you don't hit Allow within 10 seconds the dialogue will go away and never come back...unless you unpair and re-pair the device. Try doing this and seeing if the dialogue comes up. If it doesn't, it's an issue with the way your Audi/BMW polls for contacts.
BTW works perfectly with my Kenwood receiver.
Ziuck said:
If I can't get this fixed soon then I will be forced to return this phone.
How can they screw up something so simple??
Click to expand...
Click to collapse
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
hotleadsingerguy said:
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
Click to expand...
Click to collapse
I have the 08' audi a4 and my contacts sync just fine, as do the missed calls.
" my contacts sync just fine"
SIM card contacts? Google Contacts? Exactly which or what "contacts" ?
Hi, new user here to searched and figured it'd be better to post in this thread rather than starting a new one.
I'm another Atrix user who is having issues with pairing the Atrix to a bluetooth car kit. I've got the VW Touch Phone Kit (rebadged Bury CC9060) which used to work perfectly with my previous Samsung Omnia as well as my partner's Samsung S8500. The problem I have was that with the 1.57 firmware, I could initially pair the phone and it would sync the phonebook up fine so that I could make or receive any number of calls without a hitch. But the issue was when I switched the ignition off then back on, the Atrix appears to pair correctly, it'll grab the phonebook but cannot make or grab any incoming calls. When dialing from the phonebook, it will initiate the call then drop out while the call still goes through. Incoming calls just aren't picked up at all. If I deleted the pairing and paired the phone up to the car kit again, it'd work until the first ignition off and back on again.
After I updated to the 1.83 firmware, this no longer works for me at all even though it appears to pair correctly and syncs the phonebook as well.
I've looked into upgrading the software on the car kit but I'm already on v0181 which is the latest for the VW branded kit. The Bury CC9060 kit has available a v0235 update but won't load on the VW kit as it does a checksum check. I'm looking at possibly editing the flasher to bypass the checksum check.
Has anyone else used the Atrix with this car kit and experiencing the same issues?
Thanks in advance
fmflex
A quick bump.
I find it hard to believe that I'm the only one using an Atrix with this car kit...
I really wanted to buy a car kit, I was even willing to pay the rather high price. Then i saw tht the Atrix just "snaps it" with those two spring arms.
You know what happens in an accident? The phone will fly out as a missle. Good luck finding it, if you were doing 30 when you got slammed, the phone will still be doing 30 when it launches out of the clips.
If it doesn't hit you, you still won't be able to find it or call 911 on it.
So, nice dock, I'm holding off for something that can be used "in case of accident". For that price, I expect a more robust product, designed to survive. (Note to Moto, calls Mercedes and speak to crash safety team.)
hotleadsingerguy said:
"They" didn't. Audi/BMW did. They didn't spend enough time programming to figure out that Android handles contacts slightly differently. Put blame where it's due.
Click to expand...
Click to collapse
I am not sure that the blame can be directed to the car makers not suiting the android configuration.
I had concerns about Androids paring car bluetooth, so when my wife got her Samsung running Froyo before i purchased the Atrix, I tested it on my 2010 A4 and it all worked faultlessly. All phonebook, dialled, missed calls & received calls. All her contacts are stored on the Phone too, not the SIM. It actually worked better with it than my old Nokia's, and my old iPhone 3G. All of which had contacts stored on the phone not the SIM.
Being in my car all day, I had to make sure it the Atrix running Froyo would work too, and that's why I tested it with my wifes phone before buying the Atrix.
I would have to say that the problem does have something to do with how the Atrix handles bluetooth. I have been having all the same issues that other users are having.
To be fair to the Atrix, I had only one problem when I originanlly bought it and that was loading the contacts from the phones storage, all the other options were working and it never displayed the annoying error message and it never dropped the connection either.
This has only started playing up completely since I rooted it and installed HeLauncher with Fancy widgets (maybe it's just a coincidence, but its unlikely i think IMHO).
I have since uninstalled the HeLauncher and Fancy Widgets, and yet the problem is still there, so I have no realistic reason why it isn't working anymore.
Because i work for Audi, I will check at work why this issue might be happening ( just with the Atrix not all the other Android phones) and see if their is anything that can be done to fix the issue.
Hi Staunch
I'd be very interested in what you can find out about this issue. I've basically got nothing out of VW and their official stand is that the atrix isn't compatible.
fmflex said:
Hi Staunch
I'd be very interested in what you can find out about this issue. I've basically got nothing out of VW and their official stand is that the atrix isn't compatible.
Click to expand...
Click to collapse
Ok, I have tried connectivity with the current version of MMI and it seems to pair up with NO error messages at all. It would appear at this stage that the new MMI generation have the "issue" fixed. I am still waiting for a reply from Service Technical Support to answer why the issue exists on the older MMI generations. It would appear that Audi in conjection with Apple focused their MMI setup for iOS, not considering Android OS's.
Will keep you updated once I have some more information about previous versions of MMI.
Blame the cars not the phone.
My phone works 100% well and perfect with my Acura.
I've also had fun trying to get my E46 3 Series BMW ULF BT module to talk to the Atrix - has no issues speaking to an older Nokia phone. Anyway after a LOT of experimentation I've finally pinned down the root cause of the problem, text messages (SMS).
I've yet to figure out the specific trigger but it is either the number of messages or something in a specific message it doesn't like. I figured this out because I noticed the envelope icon coming up on the BMW screen for 5-10 seconds before the bluetooth would drop out each time after connecting the pairing. Each connection only lasts 15 seconds at most.
Anyway there were 193 SMS messages in the car memory, maybe the 194th message was upsetting it. I deleted almost all the 1150 SMS messages in my phone and it was only when I got rid of all of them that it connected. I then had to manually clear the SMS messages in the BMW one by one (took a long while).
I then did some testing whereby I sent an SMS or two to my phone. I noted that the Atrix seems to periodly get asked to upload messages to the car. You can delete them in the car but if they are still on the phone, they come back shortly after. They always show as unread on the BMW unless you read them on the car screen. Reading them on the phone has no affect. Maybe the SMS side of BT headset support is borked on the Atrix.
So my conclusion is that while I don't know the detailed trigger specifics, for BMWs at least the Atrix Bluetooth issue comes down to SMS messages. My large contacts directory uploads in its entirety without an issue. The solution for reliable BT connectivity to the Atrix and a BMW seems to be in SMS message management. Get yourself a copy of SMS Backup from the market when you experiment.
Hope this helps others!
Matt
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
hi! recently found, yes found freebuds , someone lost them. so unable to give them back, i decided to nurture them myself?
I myself have a samsung galaxy s9+, and have connected them to it.
I have a few issues with it even though I have updated them to the latest firmware.
my issues include:
the freebuds just disconnect every now and then, they get out of sync with one another, get interrupted when in a busy street full of cars and on top of all that, there is a massive, 1.5 second lag between the video and audio when I try to watch videos.
I earlier saw earlier people tried to switch the codec either from AAC to SBC vice versa.
though myself, I don't know what any of that means, but if it helps.... ??
does anyone have any information or tips and tricks on this?
You might have a bad batch. TL;DR version, Russian users on 4pda mentioned that with earlier batches there were problems and they got a replacement which fixed the issues such as drop outs.
Since you're not the purchasing owner but a finders keepers type of owner, you're SOL.
Hi, I'm having issues too. Were working fine but suddenly only the right one is working. I tried to pair them many times, restore the freebuds... but apparently only one is pairing my pixel 2 XL.
germao said:
Hi, I'm having issues too. Were working fine but suddenly only the right one is working. I tried to pair them many times, restore the freebuds... but apparently only one is pairing my pixel 2 XL.
Click to expand...
Click to collapse
did you solved it?
same problem here but with Galaxy s9 plus
Nope, my freedbuds are now in a drawer
polotdi said:
did you solved it?
same problem here but with Galaxy s9 plus
Click to expand...
Click to collapse
Enviado desde mi Pixel 2 XL mediante Tapatalk
Freebuds not connecting
After depleting the battery. My freebuds no longer connect by Bluetooth, instead it gives 3 different devices (box, left and right bud). I have no idea how to solve this
Reset Procedure for not pairing left or right side
Hello Friends,
If you have a huawei FreeBuds and some issues to pairing or connecting Bluetooth, then sure you are not the first one!
You can try the follow steps:
1. Put the left or right one in the case and follow the factory reset.
2 after you reset one of the pair you take out the reset one, put back the other one, and follow again the reset factory.
When you done with the second one. You take him out.
3. Close the empty case. Close your Bluetooth on your devices.
4. Open the case, put them (pair) back in the case, close case
5. Open case and follow the factory procedure.
6. Close case and start a New pairing with your phone and the free buds, but remember delete first our free buds in your phone before you pairing again your buds!
After you successfully connected, you can try a software update. Download the freebud app in google.
The old firmware is 16x, the new firmware is 19x.
The best way to update the firmware is without you have pared the freebuds in your Bluetooth list.
So delete first your pairing. Or use a other android phone.
When you follow the update, he ask to open the case and the green light go on. Press directly on update on the app. Because there is a short time the app can search the buds.
Hold your phone and buds case together. Less then 5cm.
I updated them with a Xiaomi A2 Android 8.1.0 device with the freebud app from google App Store.
Have many luck because the firmware update can stopped many times, if that happens do a factory reset with the buds inside the case. And retry a firmware update.
Don’t pairing the buds!
Good luck!
left bud issue
From the last update , initially my left bud didn't work at all, after some reset and re-pair it works but at a very low volume. In contrast the right bud works perfectly. I don't totally know how to fix this annoying problem. I tried in 100 ways also re-pairing the buds one at times but nothing works.
Someone who can help me?
I have a problem, partizlly solved.
Maybe It can help some of you.
My problem is that the noise quality is horrible.
I update, and nothing to do. It's like an old headphone, horrible !
I discover that when I go on bluetooth parameters, and parameters of the freebuds, when I take off "phone calls'' ("appels telephoniques'' in french menu), the quality instantly switch to an HD sound perfect !
The problem is that I can only use It for multimedia, and can't make a call !
If it can helps some of you !?
But is there someone who can solve entirely my problem ?
Use a Oneplus 5t.
xstu25 said:
I have a problem, partizlly solved.
Maybe It can help some of you.
My problem is that the noise quality is horrible.
I update, and nothing to do. It's like an old headphone, horrible !
I discover that when I go on bluetooth parameters, and parameters of the freebuds, when I take off "phone calls'' ("appels telephoniques'' in french menu), the quality instantly switch to an HD sound perfect !
Use a Oneplus 5t.
Click to expand...
Click to collapse
check which codec (AAC or SBC) used now. I switched off the calls, but this doesn't makes any changes, codec still SBC
It didn't work.
deefit said:
Hello Friends,
If you have a huawei FreeBuds and some issues to pairing or connecting Bluetooth, then sure you are not the first one!
You can try the follow steps:
1. Put the left or right one in the case and follow the factory reset.
2 after you reset one of the pair you take out the reset one, put back the other one, and follow again the reset factory.
When you done with the second one. You take him out.
3. Close the empty case. Close your Bluetooth on your devices.
4. Open the case, put them (pair) back in the case, close case
5. Open case and follow the factory procedure.
6. Close case and start a New pairing with your phone and the free buds, but remember delete first our free buds in your phone before you pairing again your buds!
After you successfully connected, you can try a software update. Download the freebud app in google.
The old firmware is 16x, the new firmware is 19x.
The best way to update the firmware is without you have pared the freebuds in your Bluetooth list.
So delete first your pairing. Or use a other android phone.
When you follow the update, he ask to open the case and the green light go on. Press directly on update on the app. Because there is a short time the app can search the buds.
Hold your phone and buds case together. Less then 5cm.
I updated them with a Xiaomi A2 Android 8.1.0 device with the freebud app from google App Store.
Have many luck because the firmware update can stopped many times, if that happens do a factory reset with the buds inside the case. And retry a firmware update.
Don’t pairing the buds!
Good luck!
Click to expand...
Click to collapse
Soud glitch
I ve got something like scratches or sand sound from the left Budd. I'm using One plus6
Also I cannot change the Bluetooth codec because it's always changes to the SBS
I ve just installed the latest update and it didnt make sense
i have a huawei FreeBuds and some issues to pairing or connecting Bluetooth.i tried all the above instruction still not connecting.
I have problem with my freebuds.the left buds only last 25 minutes while right is more or less 3 hours. what should I do with the left?
Just wondering if other people who own the Freebuds 3 have the same issue I have with the ANC.
So when you turn it on it does its thing, and then after a minute or so it suddenly sounds different. Like the ANC resets itself and then starts using other parameters to decide what sounds it will cancel. And it keeps doing that every couple of minutes. When it does I hear a small "plopping" noise (a bit the same as when you turn ANC on).
Just to be clear: the source of the sound I'm listening to (video, music, ...) doesn't change at all. It's purely the ANC that does something different.
And yes I'm on the latest software update and I use a Huawei Mate 20 X.
i had the same problem as you as well. i managed to do it by few steps i tried below and it work both on my pc and my huawei P20
1. Ensure the box is fully charged
2. remove the right hand side on the freebuds from the box
3.press the back button for more than 3 seconds and the blue light blinking
4.turn on your bluetooth and search
5 the blinking blue light will be faster than previous meaning other device (PC or P20) detected the freebuds
6. connect it up until successful
7.do not close the lid of the charging case.
8.insert the right hand side into the box freebuds
9.press the back button for more than 3 seconds and the blue light blinking
10. the blinking blue light will be faster than previous meaning other device (PC or P20) detected the freebuds
11 . connect it until successful
12. remove the previous freebuds from your bluetooth list
13. download freebuds assistant
14. update.
i just Performed these all steps like 10 mins ago and it works twice. hope it helps.
REPLY
deefit said:
Reset Procedure for not pairing left or right side
Hello Friends,
If you have a huawei FreeBuds and some issues to pairing or connecting Bluetooth, then sure you are not the first one!
You can try the follow steps:
1. Put the left or right one in the case and follow the factory reset.
2 after you reset one of the pair you take out the reset one, put back the other one, and follow again the reset factory.
When you done with the second one. You take him out.
3. Close the empty case. Close your Bluetooth on your devices.
4. Open the case, put them (pair) back in the case, close case
5. Open case and follow the factory procedure.
6. Close case and start a New pairing with your phone and the free buds, but remember delete first our free buds in your phone before you pairing again your buds!
After you successfully connected, you can try a software update. Download the freebud app in google.
The old firmware is 16x, the new firmware is 19x.
The best way to update the firmware is without you have pared the freebuds in your Bluetooth list.
So delete first your pairing. Or use a other android phone.
When you follow the update, he ask to open the case and the green light go on. Press directly on update on the app. Because there is a short time the app can search the buds.
Hold your phone and buds case together. Less then 5cm.
I updated them with a Xiaomi A2 Android 8.1.0 device with the freebud app from google App Store.
Have many luck because the firmware update can stopped many times, if that happens do a factory reset with the buds inside the case. And retry a firmware update.
Don’t pairing the buds!
Good luck!
Click to expand...
Click to collapse
Hi i know this is an old tread, but followed your steps, the left one has been successful factory reset, but when i do the same for the right one it doesnt work, any solution please ?