Blue tooth drop out

[cerealcable]

So for the past few weeks my HU has worked fine with my phone. I cannot explain it.

Sent from my Nexus 5 using Tapatalk

[Deathalo]

Originally Posted by SirBrass

The problem there is that the phone then undercharges when plugged into the aux usb port as the phone software won't allow the port to deliver more than 0.5A in current, thus with the newer phones, the phone's battery discharges while being charged due to the under driving, and the device gets majorly hot as well. A really DUMB thing, that, and it's the phone's firmware that's at fault there. AC charging mode, no issues.

I'd use my phone as a usb mass storage device for the HU to read files off of if it weren't for the under-charging problem.

Other than that, get an aftermarket HU. The stock Nav HU looks cool and seems cool at first until you start running into all the little annoyances and nanny features it has.

Yo! Buy this cord, it does not transmit the data portion of the usb so it acts just like plugging it into an AC jack! I have 2 and they charge my phone just as fast as at home with no usb pop up on the phone.

[ame="http://www.amazon.com/gp/product/B0088HTYUE/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1"]Amazon.com : PortaPow Specialised 5ft 24AWG Charge Only Micro USB Cable for Blackberry, Xperia, HTC One, Google Nexus, Other Fast Charging Devices : Electronics Power Cables : Electronics[/ame]

[robot]

I played with it a little this morning.

Samsung Galaxy S3 ATT with Cyanogen.
It had been working, but then decided recently to stop working and cut out and do the pair/unpair loop every 2 minutes. So, I unpaired it. Paired it back up and skipped the phone book transfer. It worked for the rest of the drive.

We'll see if it works again on the drive home.

Also, we might want to merge threads: http://www.ft86club.com/forums/showthread.php?t=50802

[SirBrass]

Originally Posted by Deathalo

Yo! Buy this cord, it does not transmit the data portion of the usb so it acts just like plugging it into an AC jack! I have 2 and they charge my phone just as fast as at home with no usb pop up on the phone.

Amazon.com : PortaPow Specialised 5ft 24AWG Charge Only Micro USB Cable for Blackberry, Xperia, HTC One, Google Nexus, Other Fast Charging Devices : Electronics Power Cables : Electronics

Problem there is that you then cannot use the phone as a mass storage device connected to the HU. That's the point. When connected as basically a usb drive for the HU to play files from, it won't charge the phone properly.

[robot]

Originally Posted by robot

I played with it a little this morning.

Samsung Galaxy S3 ATT with Cyanogen.
It had been working, but then decided recently to stop working and cut out and do the pair/unpair loop every 2 minutes. So, I unpaired it. Paired it back up and skipped the phone book transfer. It worked for the rest of the drive.

We'll see if it works again on the drive home.

Also, we might want to merge threads: http://www.ft86club.com/forums/showthread.php?t=50802

No dice. On the drive home it unpaired and paired a bunch.

[spookyz]

Originally Posted by robot

No dice. On the drive home it unpaired and paired a bunch.

Well, to add to this thread a bit (hopefully, didn't read all of it)...... but I have a Samsung Galaxy S3 (through Verizon) and it was working fine on Android 4.2, bluetooth music and phone calls, all were fine for the ~month I've had the car. This morning, Verizon pushed the 4.3 update, so I ran the update this morning, everything seemed to take fine, got in the car to go to work today and it paired/unpaired probably ~10 times streaming a podcast on a ~40 minute drive. Not sure it's specific to the 4.3 Samsung update, but it does appear to be that way from the searches I've been doing. I wish I could revert back to 4.2 but I can't find a good way to do it. If anyone has an idea on how to downgrade back to 4.2 I'm all ears.

[robot]

Originally Posted by spookyz

Well, to add to this thread a bit (hopefully, didn't read all of it)...... but I have a Samsung Galaxy S3 (through Verizon) and it was working fine on Android 4.2, bluetooth music and phone calls, all were fine for the ~month I've had the car. This morning, Verizon pushed the 4.3 update, so I ran the update this morning, everything seemed to take fine, got in the car to go to work today and it paired/unpaired probably ~10 times streaming a podcast on a ~40 minute drive. Not sure it's specific to the 4.3 Samsung update, but it does appear to be that way from the searches I've been doing. I wish I could revert back to 4.2 but I can't find a good way to do it. If anyone has an idea on how to downgrade back to 4.2 I'm all ears.

Cyanogen 10.2 (which I'm running on my S3) is Android 4.3.1 . So, yes it could be the bluetooth on 4.3 is not so great (this sort of why I started that thread in my sig).

[cerealcable]

So I'm running a Nexus 5 and it had the disconnection issue starting a few days after I had the car. Anyways, after a few weeks I turned off the bluetooth and forgot about it for at least 1-1.5 months. I recently went on a road trip so I tried it again, its been 2ish weeks without any issues.

I'm honestly baffled since my phone hasn't had any updates. I did complain about it at the dealership but they didn't claim to have done anything, but I wouldn't know.

[clintavo]

Has anyone given up and switched to the base FRS one? Is it plug and play?

[YMAA]

I'm using a Galaxy S4 (VZW) in a BRZ Ltd. My phone is rooted and running a KitKat 4.4.2 ROM, but I flash a different ROM at least once a week typically while I'm searching for one I like. Currently I'm using a ROM called Vanir with the Ktoonsez kernel.

I find my audio is pretty stable unless I'm using the Intellidemand kernel governor, then every couple seconds I get very annoying audio glitches. Using Interactive or Kconservativeq governors gives good results.

[bdbx18]

Ladies and Gentlemen,

After much internal whining and complains about the HU, I can now declare I have ZERO disconnects for the past 20 days or so. My fix is not for everyone and it's only a happenstance for me.

Over the Christmas holidays, I upgraded my HTC1's FW and ROM to 4.4 (KK). I was previously on 4.3, consistently get disconnects multiple times a day which I deduce was due to the HU because I never had any issues with my two other BT receivers in the house. But now I just don't know. My car has never been to a dealer for service and I certainly didn't mess with the HU. Only my phone's sw was updated. Go figure.

For those who care, I am on ARHD 41.0 and 4.06.1540.

[SirBrass]

For 4.3 on the s3, I found that if I wait to turn on bt after the hu boots, I get very fast connection, button response, and stable bt connection.

If I have phone bt on before hu boot up, I get massive connectivity headaches & repeated drop-outs.

Sent from my SCH-I535 using Tapatalk

[N_A]

I'm using a Samsung Galaxy S3 and I've had no issues whatsoever with the base HU. I mean I was quite impressed with how well my phone paired up with the HU. I am on a conference call every morning during my commute to work and it works flawlessly.

Now I'm thinking about upgrading to an iPhone 5S and I'm scared my BT connection is going suck with all the issues you guys have experienced.

[aschnell]

I try tried waiting to turn on the bt until after the hu was booted but never worked. Galaxy s3 Verizon 4.3 stock rooted. I deleted my txt messages and worked. When I first got my car (14 brz) it connected fine. Then one day started getting flaky? I might agree with too many txt messages breaking it based on that?