Morning all,
Like many here, I have my old N7 2012 hard wired into the dash - been running nicely for 3+ years now...
Using Timurs rom etc.
Does anyone have a solution to making and receiveing calls on the N7 (no sim capability), through a phone (OPO) connected as either Wifi (hotspot) or blue tooth?
From my own research, I dont believe the stock bluetooth stack can be used in this way - at least officially - so that would leave wifi?
Anyone done this yet?
Related
After searching this forum there is no thread on Bluetooth issues connectivity.
For a wile now i been searching the net and different sites for a fix between my phone and my car bluetooth. Before the epic i had a windows phone and the connectivity was fine including all the phonebook would load up and everything the system was build to do. With Android Epic i been having issues. Sometimes I cant connect to the car and other I am able to connect but phonebook wont load.
With all the Geniuses in the website i am sure someone can come up with a fix.
I figured i open this thread hoping we can find a final fix to retire this problem.
If it helps I am running the latest Viper Rom with Genocide kernel at 1.2ghz
However the rom did not change the statues of my issue.
Any help would be appreciated.
Thanks
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
I use this in my car: http://us.kensington.com/html/14484.html
It may cut out every 45 seconds or so but it's the only thing I've used. Got it on sale for $20.
I've got a pair of a2dp bluetooth headphones that I use to listen to podcasts via my Epic. I've had zero problems with those (using DK28 atm, for the record). So I don't think there's a hardware problem with the Epic's bluetooth.
If we're going to get some troubleshooting done, we should get a bunch of details from everyone. Like exactly what bluetooth hardware they're using, and what roms they're running.
thezero4 said:
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
Click to expand...
Click to collapse
Does everything cut out, or just Pandora? If it's just Pandora and other apps that need data connection, it might not be a bluetooth problem as much as a data connection problem.
I would suggest testing it by trying the car bluetooth with something that requires no data connection at all, like pre-downloaded podcasts.
I am talking about connectivity issues with in stock car bluetooths.
this problem is big many people been having this issue and there is a list of stock bluetooth cars that android wont pair with. I had the touch pro 2 for sprint with windows system and it worked fine in my car bought the epic and there we go. Now looks kind of bad that i would need to get an aftermarket piece to listen to bluetooth calls and load up the phonebook from android to my car.
Windows got it right even though i would never go back to a windows phone so i know there is something that android messed up here
Below i will put some links to show you how there is A LOT of people that been having this issue.
http://code.google.com/p/android/issues/detail?id=3960
http://www.google.com/#q=android+bl...start=0&sa=N&bav=on.1,or.&fp=3f40f95b1b9c7c0d
I have a 2006 Dodge Durango. It has Bluetooth. My old phone, a Samsung flip phone would connect without issue. My new phone, a Samsung Captivate, will connect most of the time, but often times, once it connects, it drops the call.
I understand this is an Epic thread, but I thought I would add my input as I am having similar problems (and this came up on my search).
If I understand you correctly, you connect some of the time and sometimes not.
Regardless, if your phone is rooted you might wanna try this.
I had a lot of issues with my bluetooth after upgrading to froyo and tried a lot of fixes including wipe3x and odin to stock....this is the one that worked for me.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Ensure that you first
- delete the car from your phone,
- delete the phone from your car,
- disable bluetooth,
- delete the file,
- CHANGE YOUR BLUETOOTH DEVICE name,
- restart,
- reenable bluetooth
- re-pair your phone with the car.
Situation:
I'm using a Xlink bluetooth gateway in my house to connect my phone with and I also have a Mazda CX-5 with integrated Bluetooth system with the latest update from TomTom and Mazda. In the Mazda, I use the Bluetooth mainly for the phone, but occasionally use it to stream audio.
Phone:
T-Mobile samsung S2 x SGH-T989D with ICS 4.0.4 (Rogers leak)
Issues:
At first (With official Gingerbread)... everything was working fine. Both device paired and all functionality worked.
Then, applied official ICS update from Kies software ICS 4.0.3 and Bluetooth issues started. I first paired my Xlink device. So far it worked. Then tried to pair my Mazda, everything was really slow but managed to have it work. Turn the car off, get back in the house and the phone is now able to pair with my Xlink device, but cannot connect as a phone audio. Even if I go manually in the Bluetooth menu and try to activate the Phone audio it wont work. Only way to have it work again is to unpaired the Mazda and reboot.
After reboot, the phone works great in the house with my Xlink device. Going back to my car and try to pair my Mazda. Same issue. The phone does pair with the Mazda, but I'm unable to make a call since the phone cannot activate the Phone audio.
Look online and have tried the ICS 4.0.4 (Rogers leak) and same issue with Bluetooth.
The only way my devices works perfectly is when I only pair with one device at a time. There is something happening when you pair more than one device, even if not both device are turned on or in range.
Anybody got the same issue or a fix to that?
Thank you and sorry if my post is a little long... but that issue is the only thing that make me not enjoy my phone.
Bluetooth cuts in and out when connected to 2 devices (car's "phone" and "media")
I have a GSM Galaxy Nexus on stock Jellybean, and bluetooth streaming works great in my car (Chevy Sonic) until I also connect the "phone" connection. When it's connected, the music cuts in and out constantly. Phone calls seem to do the same thing if "media" is connected.
If I kill 1 connection, the other works great. Is this a Galaxy Nexus problem or Jellybean? I've tried stock, franco's, trinity, etc kernels but I'm guessing this won't matter (since the source was JUST released for JB).
Does anyone else pair to multiple BT devices simultaneously? Do you have issues?
I just came from an iPhone 4S, and it paired nicely with both connections without them cutting out. I hope this is something I can get working because I use both functions all the time.
Thanks!
I connect to 2 devices in my truck and it actually seems to work better since installing Jelly Bean. On ICS I had a similar problem. My truck connects via the "phone" profile and I connect to a bluetooth adapter for the "media" profile. I could use either of them independently without a problem, but with both connected, my call quality was awful and my music would cut out periodically. I believe that the truck "phone" profile was disconnecting and reconnecting every couple minutes as I would see the display on my truck indicate that a bluetooth device had just connected.
Since installing JB, that behavior seems to have stopped. I can't say for sure as I haven't driven very much yet since installing it, but early testing seems to indicate the problem has gone away. I know this doesn't help in your situation, but I did want to share my experience as it was similar to yours.
I have a new Note 4 (Verizon) and a 2011 Kia Soul. Prior to the Note 4 I had a Note 2 (Verizon) that I paired with my car for the last 2 years without issue. I am able to successfully pair the Note 4 and the car and use all of the Bluetooth functions I would expect to work. The problem is, often (not 100% of the time), the next time I try to connect the phone to the car that connection fails. I then have to unpair and re-pair them to get them to connect. Neither side gives me anything useful in the way of error messages.
I'm at a loss as to how to troubleshoot this further. Is there a way to pull Bluetooth connection logs out of the phone?
I have the same issue, but worse. I have a 2011 KIA Sorento, and a Samsung Note 4. The Bluetooth connectivity is very intermittent. One minute is works and then stops. One minute it plays music fine and all of a sudden, the music will start going in and out, like a bad cellphone call and then disconnect. I try to reconnect and it won't. I've gotten in the car and it works great and the next time it works like crap! I've been on a cell call, talking through Bluetooth and it will automatically disconnect, but still shows connected. I have to switch to speakerphone to talk and then it all of a sudden reconnects back to Bluetooth. Does anyone know if this is a known Samsung issue? I saw a previous post from Dec 2014 which stated, " Apparently, the Note 4 and Edge all use the newest AVCRP 1.5, which nobody else uses yet. Nissan told me that they were told by Samsung, that in their next update, they're going to revert the phones back to AVCRP 1.3, which is the standard in the industry." Has this occurred?
I had the same kind of problems with my Galaxy S 6 on my 2013 F150 with Sync. I was only able to fix it by getting rid of the S6. The Note4 I had before (on 4.4.whatever) and the Note4 I have now (on 5.0.1) have no issues.
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Daimonion1980 said:
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Click to expand...
Click to collapse
Have tried different ROM's on this Pixel 3 XL so I completely understand the Bluetooth issue. Have grown to rely on turning off Bluetooth before using the passcode; kind of helps with the new ViPER4Android FX,
Since using ScorpionROM, haven't had any Bluetooth issues. Maybe give it a shot and see if it helps