Develop Bugs

Bluetooth Car Connection

I have posted this in other forums with no luck. I was hoping that maybe someone here had some answers...
I have a 2011 Ford Explorer with SYNC v2.7 (latest version until next month). It has capability to download phonebook information including photos. It is also capable of supporting SMS.
When I got the truck, I was on 2.1 (TMO-USA). The phone paired fine and people on the other end told me I sounded great. Photos from phonebook did not show up. When I tried to access messaging in SYNC, it told me phone did not support this.
I upgraded to 2.2.1 and the phone still pairs easily. Still no photos, and now SYNC recognizes that the phone has messaging capability. BUT... SYNC only randomly picks up the text messages. As near as I can tell, if I get a message just before I get in the car and start it, then there is a good chance the system picks up the message.
Lastly, now with 2.2.1, the person on the other end tells me that I sound like I am in a wind tunnel. I removed and re-synced the connection and still same thing.
QUESTIONS-
1) Anyone know what might be preventing the SYNC system from displaying my photos?
2) Anyone know why the messaging works on occasion?
3) Anyone else experience the "wind tunnel" effect?
4) Is there anything that can be done (maybe different ROM) to resolve this?
Thanks

I would advice you to try with another phone this way you might exclude the car as the reason. I suggest this because I have the feeling that the car might be the fault and the software that is incompatible with the official bluetooth standards.
If it works with other phones (maybe even Android) then the situation clears a little bit and you have a more clear way to follow.
Keep us up to speed.

Bluetooth Call Log problems.

Recently my car stereo stopped syncing the phone book and call log from my GSM Galaxy Nexus. I don't know how or why. It simply stopped working. I want to reset the connection, i tried unpairing but this didn't work. I want to actually delete the connection from the phones memory. As of now whenever I click on Bluetooth, JVC Unit is always listed there. When I first established a connection it asked if it was ok to share my phones call log and phone book, and gave a check box to remember my response for next time. I cliked OK and REMEMBER and everything was fine. Now I think it could be possible that somehow it has been set to "NO" and "Remember"(although that would be weird since I didn't mess with it) thus no matter how many times I connect, it always refuses to share. I don't know if this is really the problem, or how to fix it. Any ideas? FYI the phone works fine through Bluetooth it just has no history or data in the phone log and phone book functions.

Have you updated the ROM?
Landara said:
Recently my car stereo stopped syncing the phone book and call log from my GSM Galaxy Nexus. I don't know how or why. It simply stopped working. I want to reset the connection, i tried unpairing but this didn't work. I want to actually delete the connection from the phones memory. As of now whenever I click on Bluetooth, JVC Unit is always listed there. When I first established a connection it asked if it was ok to share my phones call log and phone book, and gave a check box to remember my response for next time. I cliked OK and REMEMBER and everything was fine. Now I think it could be possible that somehow it has been set to "NO" and "Remember"(although that would be weird since I didn't mess with it) thus no matter how many times I connect, it always refuses to share. I don't know if this is really the problem, or how to fix it. Any ideas? FYI the phone works fine through Bluetooth it just has no history or data in the phone log and phone book functions.
Click to expand...
Click to collapse
I am having the same problem on Sensation XE. It seems that with some ROMs it communicates without problems, in other cases it does not show call logs. Try to figure out what you've changed. Have you accepted any OTA?
Ciao
Rob

[Q] Problems with Google Play Music on M8

Hey everybody,
Having an odd issue with my brand new M8, which is completely stock. Few days ago I've received an firmware update (1.57.111.2 / German T-Mobile CID) for my handset. Since that update I'm not able to use Google Play Music while connected to my wlan network. It seems like, that Play Music is not able to recognize my fully functional connection and therefore refuses to download and/or stream music.
All other apps (including Spotify) are able to use my wlan connection without any problems.
Turning wlan off helps to correct that error, but that workaround burns away my included traffic
Here's what I tried without success:
1. Did a factory reset
2. Deleted all wlan connections and reconfigured them
3. Cleared Play Music's caches
4. Contacted HTC (recommended the factory reset) as well as my provider (didn't have a clue)
5. Checked the number of eligible devices with Google (currently 3 out of 10)
Now I'm a bit puzzled on how to solve this issue and wanted to ask, if anybody did experience (and maybe solved) this issue.
Best,
Marc

I'm having the same problem. I received a update from T-Mobile USA for my M8 this past weekend. Google Play Music can't keep on device or stream with "Download via Wi-Fi only" and/or "Stream via Wi-Fi only" checked in settings. I hope it's not draining my data
Sent from my HTC One_M8

smrfd said:
I'm having the same problem. I received a update from T-Mobile USA for my M8 this past weekend. Google Play Music can't keep on device or stream with "Download via Wi-Fi only" and/or "Stream via Wi-Fi only" checked in settings. I hope it's not draining my data
Sent from my HTC One_M8
Click to expand...
Click to collapse
I've discussed that issue with some German M8 users (all on T-Mobile Germany) and it appears to be limited to some Google Apps and to HTC Backup. However one user did reach out to T-Mobile and they're basically just stated, that they're currently looking into that without providing any sort of timeframe within to expect an fix for this. Downgrading the firmware fixes the problem, so T-Mobile must be the ones to blame ... very frustrating.

Hi there,
did anyone solve this issue yet? There is a few of us with an M7 that have exact same issues. I am in UK, so may not be carrier related.
http://forum.xda-developers.com/showthread.php?t=2759800

johnpgreenan said:
Hi there,
did anyone solve this issue yet? There is a few of us with an M7 that have exact same issues. I am in UK, so may not be carrier related.
http://forum.xda-developers.com/showthread.php?t=2759800
Click to expand...
Click to collapse
Hey,
Thanks for pointing that out. Wasn't aware, that this issue affects the M7 too. Unfortunately, I'm really stuck at the moment as everybody involved is pointing fingers at each others. HTC tells me, that T-Mobile messed up ... T-Mobile at least confirmed, that there might be an error. Right now I'm trying to get my M8 replaced, as somebody did break some functionality of my device. A German M8 user pointed out, that the WLAN App from Amped Wireless can be used to confirm the error, as it is not able to detect an established WLAN connection (like some of the Google apps).
However, no solutions

holychain said:
Hey everybody,
Having an odd issue with my brand new M8, which is completely stock. Few days ago I've received an firmware update (1.57.111.2 / German T-Mobile CID) for my handset. Since that update I'm not able to use Google Play Music while connected to my wlan network. It seems like, that Play Music is not able to recognize my fully functional connection and therefore refuses to download and/or stream music.
All other apps (including Spotify) are able to use my wlan connection without any problems.
Turning wlan off helps to correct that error, but that workaround burns away my included traffic
Here's what I tried without success:
1. Did a factory reset
2. Deleted all wlan connections and reconfigured them
3. Cleared Play Music's caches
4. Contacted HTC (recommended the factory reset) as well as my provider (didn't have a clue)
5. Checked the number of eligible devices with Google (currently 3 out of 10)
Now I'm a bit puzzled on how to solve this issue and wanted to ask, if anybody did experience (and maybe solved) this issue.
Best,
Marc
Click to expand...
Click to collapse
I'm really glad to have happened upon this thread, as I'm having the exact same issue on an AT&T M8 that I just purchased a couple of days ago. I updated with the new "extreme power mode" firmware, but now I can't pin music from Google Play at all. Similar explanation and attempted fixes as holychain.

I am having the same issue in Google Music. Also Google+ Fotos has the same Problem: The autosync does not recognize the wifi connection.
HTC One M8 T-mobile Germany- latest firmware 1.57.111. 2.

As posted on the other thread:
johnpgreenan said:
Guys, I found the solution to this. I am now on ARHD 71.1 with all the google apps working.
Such a simple fix (well for me) - when the phone connects to your wifi at setup, it automatically sets it as a mobile hotspot and restricts background data. It's just a tick box - go here: settings / More (under wireless & networks) / data usage / click the 3 dots top right and select mobile hotspots then untick your wifi network.
Post back if it works for you. I will post on the main ARHD thread as well as it might be something Mike was unaware off.
:laugh:
Click to expand...
Click to collapse
I still had to reboot and clear data from the app, but this is working for me. Unfortunately, Play Music is extremely slow to download music right now for me...:laugh:

dankerschen said:
As posted on the other thread:
I still had to reboot and clear data from the app, but this is working for me. Unfortunately, Play Music is extremely slow to download music right now for me...:laugh:
Click to expand...
Click to collapse
Oh thank god I found this thread. This fixed the issue for me, as well as fixing Google photos, and Flickr auto upload. I was almost beginning to regret ditching my 5S for the M8 if the whole reason for me finally switching was due to Google Music being more reliable than iTunes Match.
Whomever set that as default is a jerk.

ND8 Bluetooth issues - and workaround

After upgrading to ND8, I was really disappointed that Bluetooth would not stay connected in my car. It paired find and would happily connect. The car then sent a MAP request and a PBAP request. I accepted both (just as I would with 4.3) and all seemed to work. I could play audio and use the phone, and the car even reported that the phonebook transfer succeeded. But then somewhere between 2 and 10 minutes, it would disconnect. Then in about 15 seconds it would reconnect and be fine for another 2 to 10 minutes. And this repeats non-stop. This made phone calls almost impossible.
At first I guessed I got a bad flash. I re-flashed stock, I flashed Wicked X, then I re-odin-ed. Nothing helped. After looking at similar threads for other phones, I tried playing with WiFi settings, but that didn't do anything. Tried some Xposed settings... nope.
Finally I found that if I repaired the phone (deleting the old records on both the car and phone) and this time I refused the PBAP request, all was fine. No more disconnects!!! I don't really need my car accessing my phone book, but it was nice with 4.3 to see caller names and pictures on the car display during a call. Also I have found that an initial MAP requests is being made when bluetooth connects, but when I receive a text, I no longer get a notification on the car. So MAP is not working.
Are other people finding that MAP and BPAP are working for them on ND8? I haven't seen this reported, so I have to imagine this is not a common problem. Everything worked fine for me with 4.3 so it seems my car does support MAP/BPAP, but now there is some incompatibility and I am not sure if the bug is with ND8 or my car.
Car is a Toyota Rav4 EV. Phone is a Sprint 16G SG3.
For the MAP issue, I am wondering if I need to use Samsung Messaging to get MAP? I use Hangouts. 4.4 added a new way to select a default messaging app. In 4.3 it seemed that both apps were active, but I had turned off notifications in Messaging. In 4.4 only Hangouts is active.

It is so frustrating that the Bluetooth stack changes from version to version isn't it. You'd think they would only add features rather than break things, right?
Well, luckily I haven't had disconnect issues, but the MAP profile you are mentioning for text messages, well it comes up on the screen, but doesn't display the originator of the message in the Toyota Entune's nav screen the way it used to. Seems to display message header garbage rather than the text message originator like it used to do.
I've also noticed that the display of title metadata on the cars screen for what's currently playing isn't showing the title changes as often like it was working on 4.3.
Sent from my Nexus 7 using Tapatalk

After a bit more experimenting it seems that I was wrong. It seems that MAP is what is causing the disconnects and not PBAP. I had tested disabling MAP and PBAP together for many days which made me confident that I had found a solution. But I assumed that, of the two, PBAP was the issue. Next I tested disabling PBAP only and it seemed to be working fine so I decided my assumption was right. But I didn't test that long enough and the problem returned. I am now running with PBAP enabled and MAP disabled and it looks to be working, but its still early. I'll report back after some long drives which will test it much more effectively.
I assumed PBAP because looking through threads, others have reported disconnect issues with PBAP on other phones. It seemed a logical conclusion, but BZZZZTTTTT! OK, more after further testing...

My experience is that if I have my Sony Smartwatch 2 connected I do not have random Bluetooth audio disconnections, however if the audio accessory is the only Bluetooth device connected it will disconnect every 10 or 15 minutes. Not sure if that is helpful.
Fred

Enable / disable bluetooth turns off bluetooth tethering?

Hello,
First: All apologies for the lack of english skills.
My device is a stock HTC 10 in grey. No branding.
Android Version: 6.0.1
Patchlevel: 1. August 2016
Software number: 1.95.401.4
Description:
In order to use my TomTom go500 navigation system in the car properly i have to enable a bluetooth network connection for it. I am getting traffic data through this. And the device connects to some other sort of online services also.
Issue with the HTC10:
- I enable Bluetooth.
- I go to settings and enable bluetooth tethering.
- (At this point my navigation system can communicate fine).
- Now i drove like 160 kilometres to Bodensee and left the car.
- Turned off bluetooth.
- Went around Bodensee and took many pictures and did some other crazy stuff.
- Got in the car again.
- Turned on bluetooth.
- Ran into heavy traffic on my way home until i noticed i got no traffic data.
- Blamed my TomTom
- Found out the Issue was that Bluetooth tethering got turned off automatically.
- Decided to not blame my HTC10 but ask if others had the same issue or a possible fix?
Do you?
In short the title says it. Do you have the same issue? A fix? Do you know if that is reported to HTC already and if it is maybe being worked on?
Many thanks!
Greetings,
R

revealed said:
Hello,
First: All apologies for the lack of english skills.
My device is a stock HTC 10 in grey. No branding.
Android Version: 6.0.1
Patchlevel: 1. August 2016
Software number: 1.95.401.4
Description:
In order to use my TomTom go500 navigation system in the car properly i have to enable a bluetooth network connection for it. I am getting traffic data through this. And the device connects to some other sort of online services also.
Issue with the HTC10:
- I enable Bluetooth.
- I go to settings and enable bluetooth tethering.
- (At this point my navigation system can communicate fine).
- Now i drove like 160 kilometres to Bodensee and left the car.
- Turned off bluetooth.
- Went around Bodensee and took many pictures and did some other crazy stuff.
- Got in the car again.
- Turned on bluetooth.
- Ran into heavy traffic on my way home until i noticed i got no traffic data.
- Blamed my TomTom
- Found out the Issue was that Bluetooth tethering got turned off automatically.
- Decided to not blame my HTC10 but ask if others had the same issue or a possible fix?
Do you?
In short the title says it. Do you have the same issue? A fix? Do you know if that is reported to HTC already and if it is maybe being worked on?
Many thanks!
Greetings,
R
Click to expand...
Click to collapse
I did not encounter this since i did not use bluetooth tethering. Just tested it, activated bluetooth, then activated tethering and deactivated bluetooth which in turn deactivated tethering. Wouldn't call this a bug, seems more like common sense to me that deactivating bluetooth also deactivates bluetooth tethering.
If i'd stop watering my plants until they are dried out, then start watering them again i do not think "man, why won't they grow"
*sorry for the non-technical example, it's late and this was the best i could come up with

Hi there
Sure, turning BT back on the tethering still keeps turned off. It worked with my HTC One S. It just remembered my setting. This is the fourth HTC smartphone i own. And i'm just used to this until now.
I would have expected it to behave like remembering my settings. What i understand already is that the visibility option happens automatically.
It is a bit annoying that i have to walk through several menus to reactivate Bluetooth-Tethering. Ehm in the meantime i found a bugreport on via online research. (All my excuses for the external link):
https://code.google.com/p/android/issues/detail?id=161031
Some mentionings are no resolution there until now. I guess this is up to the devs. And i think many ppl have this issue. Not just HTC10. I hope they make this work again.
Also i will try the there mentioned workaround with a tool from the market.
Many thanks for your help!
Greetings,
R

I just wanted to popp in and say that i chatted with the support at HTC website. They let me boot the HTC10 in safe mode and asked me to reproduce the issue.
I reproduced it instantly. Further we sorted the steps to reproduce to full understanding.
The HTC employee forwarded the issue to the dev team.
Further i was informed that i will receive information on this issue in future.
Greetings,
R