Jelly bean update and bluetooth Calling issue

[juanoli]

Found this on a developers site and it worked with my 2011 Honda Odyssey:

. When you start your phone or restart bluetooth go to Settings>Applications>Running Services. Look for the Service "BluetoothPbapService". tap it, then hit stop. This removes it from the list. The phone pairs and uploads the phone book without problems until you either stop and restart bluetooth or turn your phone off. I am looking for a developer who can automate this process with an app without rooting the phone. Hope this helps.

It worked for me!!! First time. I even deactivated the bluetooth connection on my cell phone and reactivated it. The coupling with my car handsfree system worked again with no disruption and no need to reset anything else.

Great find!!! Thanks a lot!

 

[notanexpert]

S4-At car, I dumped the phone connection. At phone I dumped the car connection. Restarted phone. Restarted car and paired phone. TURNED OFF MEDIA PAIRING -- PHONE ONLY.
Paired phone with car. WORKS FINE.
I have not yet tried the media connection, but it was the phone I wanted got an RCA plug for music.

 

[Comp625]

I'm glad I found this thread!

Add me to the list. I have a 2010 Nissan Maxima with Navigation/Tech package and I've had Bluetooth distortion/robotic/wind tunnel call audio issues on BOTH my old Samsung Galaxy Nexus (which had ran on Android 4.2 and 4.2.1) as well as my Samsung Galaxy sIII (which is running on Android 4.1.2). Granted, I have the Verizon version of the sIII but the issue seems to plague s3's in general and is widespread among many car manufacturers.

To be clear, I do NOT have any connect/disconnect issues.
Also, I do NOT have any media streaming issues. My issues are strictly with phonecalls. I can hear the other caller but they can barely hear me.

Are there any solutions available (as this post hasn't really been updated since August)? Although I'm rooted and am running a customized version of Touchwiz 4.1.2, I'd rather not flash over to an AOSP-based ROM that uses 4.2.2 as there are known issues (e.g. non-Touchwiz camera doesn't work as well).

 

[AdamBAtl]

An update to Sprint users.

After a very long wait, I just got an update a few minutes ago that finally fixed my bluetooth issue! The update is about 103MB in size and included new features such as multi-view. I tested my BT on my 2007 G35 right after the update and voila! Give it a try, good luck all!

intelliboy,

Can you confirm the issue you say is fixed? Is it the garbled/robotic sound issue on the 2007 G35 with Galaxy S3?

I've had the same issue for over a year. Only, I knew it was a potential problem because my older Google Nexus S had the same issue when it upgraded from Gingerbread to ICS. So, when my S3 started telling me it wanted to upgrade to JellyBean, I went back to my Sprint store and tried it with one of their upgraded S3s. It had the issue. So, for over a year, I have been refusing to let my S3 upgrade.

Are you saying that I can now let it upgrade and the newest firmware from Sprint will correct the issue?

Thanks.

 

[riahc3]

I want to come by to confirm that this is a Android issue. Nothing with carrier and nothing with maker.

One of the Bluetooth modules complied for 4.1.x's kernel is kind of glitchy.

4.2.2 fixed streaming issues and 4.3 introduced some more Bluetooth profiles which might or might not help.

The only solution is wait for a update from your carrier or install a custom ROM with at least 4.2.2 (although I highly recommend at least 4.3)

 

[Comp625]

I want to come by to confirm that this is a Android issue. Nothing with carrier and nothing with maker.

One of the Bluetooth modules complied for 4.1.x's kernel is kind of glitchy.

4.2.2 fixed streaming issues and 4.3 introduced some more Bluetooth profiles which might or might not help.

The only solution is wait for a update from your carrier or install a custom ROM with at least 4.2.2 (although I highly recommend at least 4.3)

For those who root and flash custom ROMs, can you comment on whether a custom 4.3 ROM (e.g. CyanogenMod 4.2) has fixed your Bluetooth car/voice issues?

 

[Comp625]

S4-At car, I dumped the phone connection. At phone I dumped the car connection. Restarted phone. Restarted car and paired phone. TURNED OFF MEDIA PAIRING -- PHONE ONLY.
Paired phone with car. WORKS FINE.
I have not yet tried the media connection, but it was the phone I wanted got an RCA plug for music.

I think I will try this (Unpair Media and only keep Hands Free paired) with my '10 Maxima and report back. The downside is that I do listen stream audio quite a bit (e.g. Pandora), but luckily, I have RCA plugs and I'll buy an Aux Adapter.

Either way, let's hope this potential "fix" will last until Touchwiz based off of 4.3 or 4.4 is released. Again, I assume BT problems would be alleviated by then.

Sent from my Samsung Galaxy s3 via Tapatalk Pro

 

[AdamBAtl]

intelliboy,

Can you confirm the issue you say is fixed? Is it the garbled/robotic sound issue on the 2007 G35 with Galaxy S3?

I've had the same issue for over a year. Only, I knew it was a potential problem because my older Google Nexus S had the same issue when it upgraded from Gingerbread to ICS. So, when my S3 started telling me it wanted to upgrade to JellyBean, I went back to my Sprint store and tried it with one of their upgraded S3s. It had the issue. So, for over a year, I have been refusing to let my S3 upgrade.

Are you saying that I can now let it upgrade and the newest firmware from Sprint will correct the issue?

Thanks.

I just wanted to let other readers know that this worked. I let my phone upgrade (on Sprint). It went through three upgrades, asking me to upgrade and re-starting the phone each time. When it was done, on I was on Jellybean 4.1.2 and my Bluetooth connection to my car worked perfectly.

 

[Comp625]

I'm happy to report that switching over to Android Open Source Project 4.3 improved my Bluetooth experience. Mind you, I am on Verizon and that carrier has yet to release Android 4.3, so my usage is based on a "custom ROM." If you are comfortable with flashing custom ROMs, by all means, I highly suggest AOSP 4.3 over Touchwiz. Below are some stray observations after having used BoneStock 3.4, HyperDrive RLS16 and CleanROM 7 (all are Touchwiz ROMs based on the stock Android 4.1.2 that comes with the phone). The AOSP ROM I'm using now is called "CarbonROM" - nightly 11/14 based on Android 4.3.1.

Bluetooth (a recap of what I posted previously in this thread):
- On Touchwiz, I had a ton of Hands-Free call quality issues but my A2DP Media Streaming was fine. Callers would often say that my words and sentences were cutting out A LOT, and that I would sound robotic. Touchwiz 4.1.2 uses Samsung's proprietary Bluetooth stack.
- On AOSP 4.3.1, it looks like Google's Bluetooth stack works for me. Call quality is better (not perfect but at least usable now) and media streaming still works perfectly like it did before.
- Also, if my phone is connected via Bluetooth but nothing is streaming, I can now initiate voice commands (e.g. in Google Now) and it works as it should. Before on Touchwiz, I had to begin streaming something (e.g. Pandora) in order for voice commands to work -- otherwise, it would stay stuck and not accept any speech.
- IMO, Bluetooth compatibility still seems to be a hit-or-miss/luck-of-the-draw experience for most devices regardless of what Bluetooth stack being used. I simply lucked out.

Speed: People aren't kidding when they say that EVERYTHING is way smoother with AOSP. Here are some examples...
- My Notifications Pull-Down was always a bit laggy with TW -- that is not the case with AOSP.
- Opening, switching, and closing apps is now instantaneous.
- On Touchwiz, my "Available Memory" (RAM) would hover around 30% on medium-use and sometimes dip to the 8-10% range.
- With AOSP, I'm averaging around 30-40% with lots of stuff open, or around 60% on light use right after rebooting. It goes to show that Touchwiz eats up a lot of memory by default. Note: I used and continue to use the "Greenify" app to suppress apps from staying in memory.
- I'm sure the bump in speed is also attributable to the custom Cyanogenmod kernal that is used in CarbonROM.

Signal: My girlfriend has an S4 and I was able to draw comparisons side-by-side against my S3. When I was still on Touchwiz, my signal strength was nearly identical to her S4. Since switching over to AOSP......
- According to the popular "Network Signal Info" app, my phone would consistenly hover around 4dBm to 8dBm weaker than my girlfriend's S4. For example, in weaker signal areas, she'll pull in -100dBm but I'll hover around -105dBm. In my opinion, the drop in signal quality is NOT a dealbreaker for moving over to AOSP. I have yet to drop a call or be unable to make a call in all of my usual places.
- Based on the graphs in the "Network Signal Info" app, her stock S4 was more 'stable' with signal strength, whereas I saw tiny fluctuations (+/- 1dBm to 3dBm) on my phone. Her signal flat-lined more often, which IMO, is a good thing. Note: both phones featured similar ASU's (the frequency at which the signal is being updated).
- For anyone who doesn't know, Samsung does not open-source its RIL code. So the signal code in AOSP is essentially "reverse-engineered" to work with the S3 -- hence why signal strength varies.

Camera: I always found the Touchwiz camera to be a nuisance to use. IMO, from a practicality perspective, the camera quality with AOSP seems to be the same.
- Pictures of my cat always came out blurry (poor low-light capabilities) or mis-focused under TW, and continues to be the case with AOSP.
- I also appreciate the 4.3 menu interface (e.g. click on the screen and with 1 thumb drag, I can change Exposure, White Balance, etc.). These settings were a nuisance to pull up on Touchwiz.
- Oddly enough, under both TW and AOSP, I was never able to successfully change Exposure value. A +2.0 or -2.0 did nothing to the end photograph.
- Mind you, I am a borderline pro-photographer, so I definitely know what I'm doing when it comes to Exposure values, White Balance, etc.

I hope that my user testimonial will help those who are on the fence about jumping to an AOSP ROM (and/or learning about how to unlock, root, and flash a Custom ROM)!

 

[hollie53151]

I have an Infiniti q50 and a Samsung galaxy note 3. I can receive calls through the Bluetooth with no problem, but If I make a call through Bluetooth the call fails unless I manually unlock my phone. Where we live you can not be seen touching your phone while driving. So, I have a very nice car and a great phone that can't communicate well. Ive had cheaper cars and phones that worked like a charm. I called Samsung - they had no solution and blamed Infiniti. I brought the car to the dealer - after having my car all day and resetting all my setting to default, their conclusion was to uninstall my phone from Bluetooth and resolve to not having any phone in my car. Really? That is my solution? There must be a work around permissions and Bluetooth somehow! Anybody have any suggestions?

 

[IAPNMC]

I had the same issue some time ago with not even a recognition from Samsung that I had a problem! My solution was to give my Android phone to my kid, and I got an iPhone in an upgrade deal. It works MUCH better, clearer, with no set up problems, and I REALLLY love the iPhone as well. Made an Apple fan out of me. Even tho I did buy a Samsung tablet which I also really like, the iphone solution for the car is painless and works great.