Related
I use my Diamond as an MP3 player way more than a phone. I also use a Sony Ericsson Bluetooth Headset HBH-DS970 all the time. But very often I'll be listening when boom! The sound stops for some unknown reason. Many times it's a brief second or two and it starts again. Other times I reach into my pocket and hit the power button and poof, it starts again. Annoyed I put it back in my pocket.
Then sometimes it doesn't come back to life. Of course, I'm driving at the time and have to fiddle with the phone and drive, which is very dangerous.
Very often the bluetooth just drops. I have to go in, hit the power button, slide to unlock, Start: Settings: Connections: Bluetooth: Mode and I see the Turn on Bluetooth and Make this device visible to other devices toggled off even though I can see the little Bluetooth icon in the title bar is still on! I toggle on these and hit OK. Often I need to power off and back on my HBH-DS970 to re-establish the Bluetooth connection. Now the HTC Touch Diamond does not play a sound when the bluetooth establishes itself like my old PPC-6700 so I just guess and hit play on the HBH-DS970. Sometimes the I have the Wireless stereo portion working but the AVRCP is not working so play on the HBH-DS970 doesn't work and I have to hit play on the HTC Touch Diamond (Sprint Music). Later I'll find that Wireless stereo is working but Hands Free is disabled.
So why does this happen? Why does the Bluetooth drop at all? Is there any better Bluetooth stacks that have less bugs that I can install. I recall tell about something like a Widecom Bluetooth stack or whatever. Is that any better?
Recently I purchased a Motorola Rokr unit which is a unit for your car that receives a Bluetooth signal and rebroadcasts it to FM for your car stereo. It works great but the having to transfer Bluetooth pairing from my headset to the Rokr when I get in the car never goes smoothly. I have to remember to pause the program, stop the Bluetooth going to the headset, turn on the Rokr, it attempts to connect to the phone and it cannot if the phone is talking to the headset via Bluetooth. Why's that an issue? Why can't the Bluetooth talk to more than one device at the same time?!? I mean what if I want the Bluetooth music or program to go to two headsets simultaneously or to the headset and the Rokr? Shouldn't that be my choice.
Next I need to tell the Rokr to transmit on FM and establish that connection. Then I try to hit the pause/play button on the Rokr and often again, the Wireless is paired up to the Rokr but the Hands Free isn't. Get out the phone, power button, slide to unlock, Start: Settings: etc. etc. - what a pain.
Then I'll be driving and listening and life is good when suddenly again, the connection drops. The Rokr cutely has a female voice that comes on through the radio saying "Connection dropped". Yeah I know - and I'm not impressed!
Repeat procedure in reverse when leaving the car transferring the Bluetooth signal from the Rokr -> HBH-DS970.
LIFE SHOULD NOT BE THIS DIFFICULT!!!
So I ask:
. Is there a better, more reliable Bluetooth stack I can install?
. If not, are there some registry settings that I can tweak to make Bluetooth more reliable? I have used the Advanced Configuration tool and saw some settings about Bluetooth sound quality but I don't know if upping th quality had lessoned the reliability...
. What are some of the reasons that a Bluetooth connection will drop? I mean it's not like I've walked outside of its broadcast range - hell I'm still in the car!
. Finally, is there anything I can do to lesson the amount of short micro drops of 1/2 - 1 second? It's a little annoying when you're grooving to a tune and that happens.
Thanks.
Try this for some answers http://forum.xda-developers.com/showthread.php?t=432072
OT, can you record sound via BT headset's microphone? Not being able to do that annoys me much and still haven't got any answers from anybody.
I use the Bluetooth with phone calls. With Vito's Audio Notes I can record phone calls and hear both me and the caller in the recording - through the Bluetooth. I see Vito also has a "finger friendly" recorder but I'm not interested in that. However it seems clear the audio path from Bluetooth mic to recording can work.
Thanks for the pointer to that thread however the concern there is about Bluetooth quality not Bluetooth reliabiliy. Personally my Bluetooth quality is just fine - when the Bluetooth remains connected that is! I'm puzzled why you would have read my post and thought I wanted better Bluetooth quality?
I have been streaming audio since i got my HTC Wizard - 2 phones ago..
Back then, i was running WM5 and it had notoriously bad BT stack (really bad quality of A2DP audio). No tweak could eliminate the horrible high-pitched noise.
Fed up with the terrible sound, i tried the Widcomm stack.
This dramatically improved audio quality, but the Widcomm stack had other problems; i was not able to use any of my other BT devices. (back then i had a seperate GPS device and a Jabra wireless earpiece).
Eventually i managed to have both BT stacks installed, so i could choose which stack to start, depending on what i was going to use.
However, this was still far from perfect, because i wanted to be able to use my earpiece, use Tom Tom and listen to music at the same time (in my car).
The solution came (for me) with WM6, it had a really improved BT stack, the A2DP audio sounded much better.
For other applications the Microsoft stack worked well from the beginning.
When i just started using WM6 it did need some (registry) tweaking to overcome the problem of the "skipping" that sometimes occurred (those skips were not due to disconnection problems, it was just a matter of figuring out the highest bitrate the device could handle! (=>higher bitrate = better sound, more bandwidth, higher chance of music "skipping", =>lower bitrate = more stabile connection (less "skips", at the price of lowering the audio quality)).
Since my last phone (HTC touch) i did not even need to apply that tweak anymore, standard settings worked fine for me (acceptible audio quality, no 'skipping' problem).
Today i have a HTC Diamond, and i use a MBR-100 to stream audio to, i hook this device up to my car stereo (in fact, i have two, so i never run out of battery power).
I use my Jabra earpiece simultaneously.
I have no complaints whatsoever.
So to answer some of your questions, based on my own findings :
- The WM6 BT stack is capable of handling multiple connections at the same time (in my case, A2DP, remote GPS and Jabra earpiece)
- I never had a disconnect from my MBR-100 (which is also from sony Ericsson) without reason.
- I recently discovered,i can activate A2DP just by pressing the button on the MBR-100. Before, i always activated the connection by going to => settings=> Bluetooth etc. Maybe you have a button that does that on your headset? If so, it will at least save you the trouble setting up the connection again on your Diamond...
Finally, i don't know which ROM you are using, but the one i'm running now is the one from the official HTC website, "_HTC Touch Diamond_QMR_RUU_Diamond_HTC_NLD_1.93.404.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe".
One more thing :
- It is not possible to stream A2DP to more than one device at the time.
However, i found a nice little program to switch the A2DP stream between paired BT devices in reach.
It can also toggle the sound (and mic) from a phone call between my earpiece and the internal speaker.
Maybe it is useful for you as well : LINK
Copy .exe to the phone and execute there (when you have a A2DP connection running).
PaWs said:
OT, can you record sound via BT headset's microphone? Not being able to do that annoys me much and still haven't got any answers from anybody.
Click to expand...
Click to collapse
After toggling the sound by means of the program i mentioned in my previous post (This one) it definately records sound trough the earpiece (it's a Jabra BT350).
Thoroughly tested, 100% sure.
TheMusicMaster said:
I have been streaming audio since i got my HTC Wizard - 2 phones ago..
Back then, i was running WM5 and it had notoriously bad BT stack (really bad quality of A2DP audio). No tweak could eliminate the horrible high-pitched noise.
Fed up with the terrible sound, i tried the Widcomm stack.
This dramatically improved audio quality, but the Widcomm stack had other problems; i was not able to use any of my other BT devices. (back then i had a seperate GPS device and a Jabra wireless earpiece).
Eventually i managed to have both BT stacks installed, so i could choose which stack to start, depending on what i was going to use.
However, this was still far from perfect, because i wanted to be able to use my earpiece, use Tom Tom and listen to music at the same time (in my car).
The solution came (for me) with WM6, it had a really improved BT stack, the A2DP audio sounded much better.
For other applications the Microsoft stack worked well from the beginning.
When i just started using WM6 it did need some (registry) tweaking to overcome the problem of the "skipping" that sometimes occurred (those skips were not due to disconnection problems, it was just a matter of figuring out the highest bitrate the device could handle! (=>higher bitrate = better sound, more bandwidth, higher chance of music "skipping", =>lower bitrate = more stabile connection (less "skips", at the price of lowering the audio quality)).
Click to expand...
Click to collapse
Would you happen to recall what those registry tweaks were? Based on your above comments I think the best I can do is to lower the bit rates and bandwidth. Honestly most of my listening is talk radio and much less music. Even so, I'm older and I can't tell as much about the lose of highs, etc...
I have toned down things in Advanced Configuration Tools - Bluetooth section hoping that this increases reliability.
What I don't understand is why is this apparently so hard to get right? I mean this is not rocket science here! It's merely a connection that is radio based? Can't people code the software correctly! Geeze!
Since my last phone (HTC touch) i did not even need to apply that tweak anymore, standard settings worked fine for me (acceptible audio quality, no 'skipping' problem).
Today i have a HTC Diamond, and i use a MBR-100 to stream audio to, i hook this device up to my car stereo (in fact, i have two, so i never run out of battery power).
Click to expand...
Click to collapse
My car doesn't have an audio in, nor does it have Bluetooth (they're trying to sell you the OnStar crap).
I use my Jabra earpiece simultaneously.
I have no complaints whatsoever.
Click to expand...
Click to collapse
I don't have any earpieces. I don't know why I need an earpiece to stick in one year and hear things in mono with one ear when I already have a stereo head set that does this in both ears.
So to answer some of your questions, based on my own findings :
- The WM6 BT stack is capable of handling multiple connections at the same time (in my case, A2DP, remote GPS and Jabra earpiece)
Click to expand...
Click to collapse
Later on you correct yourself saying you can't do two A2DP's at the same time. That was specifically what I was asking about - a car A2DP and my headset A2DP (Or say two people with the same A2DP headsets, etc). I don't understand why this is limited. It seems artificial.
- I never had a disconnect from my MBR-100 (which is also from sony Ericsson) without reason.
Click to expand...
Click to collapse
What would be a valid reason for disconnection?
- I recently discovered,i can activate A2DP just by pressing the button on the MBR-100. Before, i always activated the connection by going to => settings=> Bluetooth etc. Maybe you have a button that does that on your headset? If so, it will at least save you the trouble setting up the connection again on your Diamond...
Click to expand...
Click to collapse
The Rokr has essentially 4 buttons. Power, FM selector, Call pickup and Pause/Play. There are also some combinations. The FM Selector is simply a button to push where the Rokr scans the stations and tells you which station to set your FM radio to. Power is for power, naturally. The Call pickup and Pause/Play are as their names suggest. Pause/Play pauses or plays the media player on the other end of the Bluetooth (through AVRCP) and Call pickup picks up an incoming call. Both of these buttons attempt to talk to the remote Bluetooth device if the connection is not currently established. However since most of the time the problem is that the Bluetooth dropped it's connection (necessitating having to go throught Start: Settings: Bluetooth: Mode: Turn Bluetooth on). Also, turning off the power and turning it back on causes it to try to pair up again, which sometimes work. However, if you currently have it broadcasting to your FM radio and your radio turned up, powering it off kills that connection causing loud static to come out of your radio until you power it back up and re-establish the FM broadcast portion.
I can see if I can screen capture my HTC Touch Diamond with the Bluetooth off in the Bluetooth settings but the Bluetooth indicator actually on in the title bar. Weird state! You should never be in that state with one part saying Bluetooth is on and the other saying Bluetooth is not on!
Finally, i don't know which ROM you are using, but the one i'm running now is the one from the official HTC website, "_HTC Touch Diamond_QMR_RUU_Diamond_HTC_NLD_1.93.404.1_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe".
Click to expand...
Click to collapse
I'm using whatever came on my Sprint version of the HTC Touch Diamond.
Do you know of a Widcomm stack for the HTC Touch Diamond? How about a copy of the MS Bluetooth stack? I did turn down the bandwidth/bitrates and hopefully that'll make it more reliable. However it would be nice to have those Bluetooth stacks available to install and play with.
TheMusicMaster said:
One more thing :
- It is not possible to stream A2DP to more than one device at the time.
However, i found a nice little program to switch the A2DP stream between paired BT devices in reach.
It can also toggle the sound (and mic) from a phone call between my earpiece and the internal speaker.
Maybe it is useful for you as well : LINK
Copy .exe to the phone and execute there (when you have a A2DP connection running).
Click to expand...
Click to collapse
I had seen this program before. Perhaps you can explain how it's supposed to work. Because whenever I run it it does nothing.
I have two HBH-DS970's. I pair them both up to the phone. I can play music but only through one of them. When I run the Bluetooth toggle thing it first plays in the current HBH-DS970 but pretty much out of phase (sounds tinny). If I run the BT Toggle again it briefly (for 1/2 a second) plays on the speaker phone then plays in the same HBH-DS970 but in phase (full bass). The toggle toggles between these two in phase/out of phase sounds with a brief blast on the speaker phone but only in one of the HBH-DS970.
If I power off the HBH-DS970 and establish Bluetooth connections with the other HBH-DS970 and I do the BT Toggle thing again the same thing happens with the second HBH-DS970. It does not transfer the BT from one HBH-DS970 to the other! I suspect it wouldn't transfer the BT from an HBH-DS970 to the Rokr either.
I don't get it! What's this BT Toggle for?
defaria said:
Would you happen to recall what those registry tweaks were? Based on your above comments I think the best I can do is to lower the bit rates and bandwidth.
Click to expand...
Click to collapse
You're correct. They are the same tweaks that are now provided in the advanced configuration tool. Back then, when i just had my Wizard i did not have this tool and i had to go into the registry to change the settings manually (they can be found under \HKLM\Software\Microsoft\Bluetooth\A2DP\Settings).
The most important one is BitPool, i use 58 for the quality of the audio, but since you mentioned you use it to talk radio and not so much listening to music you can set it to 30. You should not experience any buffering skips then.
Then you have MaxSupportedBitPool, which you can delete. I played with changing the settings here but no major effect.
Finally, there is UseJointStereo, to have stereo set it to 1. In the older WM6 BT stacks when set to 0, it would reduce the hissing noise but the audio would be mono.
defaria said:
I don't have any earpieces. I don't know why I need an earpiece to stick in one year and hear things in mono with one ear when I already have a stereo head set that does this in both ears.
Click to expand...
Click to collapse
I only use the earpiece to make calls while driving, not to listen to music..
defaria said:
Later on you correct yourself saying you can't do two A2DP's at the same time. That was specifically what I was asking about - a car A2DP and my headset A2DP (Or say two people with the same A2DP headsets, etc). I don't understand why this is limited. It seems artificial.
Click to expand...
Click to collapse
My MBR-100 uses A2DP, my earpiece HFP. That's why i'm able to use both at the same time. However, you can't use A2DP 2x simultaniously. I was just pointing out that the BT stack of WM6 is capable of using different profiles simultaniously. If your Rokr and your Sony headset use different profiles, you could have used the small BT toggle program to switch easily..
But even if they use different profiles, you can't use the audio output twice at the same time. You can only toggle to wich profile it redirects.
defaria said:
What would be a valid reason for disconnection?
Click to expand...
Click to collapse
The only thing i can think of, is when the two are too far apart from each other. I did not have any strange disconnects so i don't have the same experience.
You mentioned you are still running the original ROM, and if you have the time it is not a bad idea to upgrade it. I know that in the beginning of WM6 A2DP did not work as well as it does today (i had to tweak then, now it works well with default settings). Also because you mentioned your BT behaves irratically.
The process of upgrading is relatively easy and you will gain a performance boost as well.
defaria said:
Do you know of a Widcomm stack for the HTC Touch Diamond? How about a copy of the MS Bluetooth stack? I did turn down the bandwidth/bitrates and hopefully that'll make it more reliable. However it would be nice to have those Bluetooth stacks available to install and play with.
Click to expand...
Click to collapse
Since i had my Diamond i never had problems with BT so i didn't search for that. I did save some of the stacks i experimented with when i had my Wizard, but i dont know if they will work on te Diamond... If you can't find anything on this forum, let me know and i will post the cab's for you.
But again, i don't know if they will work on te Diamond!v
defaria said:
I had seen this program before. Perhaps you can explain how it's supposed to work.
....
I suspect it wouldn't transfer the BT from an HBH-DS970 to the Rokr either.
I don't get it! What's this BT Toggle for?
Click to expand...
Click to collapse
The BT toggle app does nothing more than redirect the audio to the next available (connected) device. I use it switch to earpiece, when i answered the phone with the buttons on the Diamond (when i answer calls with the button on the earpiece, it does that automatically).
When listening to music, i can switch the audio between the earpiece and the car stereo.
So i figured, maybe you could use it in the same way, when you walk to the car enjoy the music trough your headset, and when you are in your car, click whatever button it is on your Rokr that activates the connection and simply click the icon to change the audio from your headset to the Rokr.
edit :
After reading your story about your Rokr again, i begin to believe there is something wrong with the BT portion in your Diamond (connection dropping, having different icons say different things about BT state). Your Rokr wants to make the connection by pressing the button, and that is how easy it should be.
That's how it works for me. I would recommend upgrading to the latest ROM, i downloaded it from the official HTC website.
I mentioned the exact filename with version number a few posts ago.
That way, you will be sure that software (BT stack) is o.k., i can confirm that in my case it does what it is supposed to...
TheMusicMaster said:
I only use the earpiece to make calls while driving, not to listen to music..
Click to expand...
Click to collapse
But my point is that the HBH-DS970 can do both. IOW while listening to music (or talk radio), if a call comes in then you simply hit the little call switch on the mic and the music stops and you answer the phone. Talk on the call and listen in both ears then hit the little call switch on the mic and wham you're back to your music or program material. It's really quite cool! When it works that is! Or, if you weren't listening to music and a call comes in simply put the earbuds in (they conveniently fall along the necklace of the HBH-DS970) and talk. IOW, given this, what would I need or want a mono earpiece that just answers calls when this will do both?
My MBR-100 uses A2DP, my earpiece HFP. That's why i'm able to use both at the same time. However, you can't use A2DP 2x simultaniously. I was just pointing out that the BT stack of WM6 is capable of using different profiles simultaniously. If your Rokr and your Sony headset use different profiles, you could have used the small BT toggle program to switch easily..
Click to expand...
Click to collapse
Define "different profiles" in this context...
But even if they use different profiles, you can't use the audio output twice at the same time. You can only toggle to wich profile it redirects.
Click to expand...
Click to collapse
That may be what the BT Toggle does and it may be that you cannot use two A2DP stereo outputs at the same time. What I'm asking is "Why not? Why this seemingly artificial limitation? Is is security concern? Did nobody think anybody might want to do this? Is it a hardware limitation? Is it a Bluetooth 2.x limitation?". It just seems silly to me to put a limitation like this for seemingly no particular reason. Ya know some people might want to actually share their music in like real time!
You mentioned you are still running the original ROM, and if you have the time it is not a bad idea to upgrade it. I know that in the beginning of WM6 A2DP did not work as well as it does today (i had to tweak then, now it works well with default settings). Also because you mentioned your BT behaves irratically.
The process of upgrading is relatively easy and you will gain a performance boost as well.
Click to expand...
Click to collapse
I've done some ROM updates back with the old PPC-6700. Yes there were better but they also weren't supported. I'm with (crappy) Sprint but I think all carriers shy away from you burning in a new ROM on them. They only support you not touching anything like that. In fact, IIRC the original Sprint ROM for the PPC-6700 didn't even support stereo Bluetooth at all! It was only after installing the Widcomm stack that I was able to get stereo BT working!
And that's part of the scary part for me. Originally, the first BT stack I installed worked fairly well with MS Voice Command actually working and when a call came in while I was listening to music, it would properly pause the music, answer the phone then return to the music. But that lasted only a short time. For most of my 2 years with that phone the BT would not stop the music to answer the phone.
The current Sprint derived HTC Touch Diamond ROM works WRT the BT behaving properly for stuff like that. The only real problem I'm having is with the dropping of the connection. So if I go to a new ROM and that breaks... well I don't want that happening. Perhaps if you could point me to the original Sprint ROM so I can get back to where I'm currently at I would venture into newer ROMs.
But another thing that would make me go for the new ROMs is if I could get rid of the god awful Sprint Music Player (SMP or actually the HTC Audio Manager and its Today plugin)! This thing sucks! I usually use Pocket Player however the god damned SMP steals the AVRCP controls such that Pocket Player cannot get them. So I can't use Pocket Player and then have the Play/Pause button on my HBH-DS970 play or pause the SMP! You end up having two audio streams playing at the same time and the pause button does not pause Pocket Player! If there's a ROM out there that removes the silly SMP then I'm all ears!
Since i had my Diamond i never had problems with BT so i didn't search for that. I did save some of the stacks i experimented with when i had my Wizard, but i dont know if they will work on te Diamond... If you can't find anything on this forum, let me know and i will post the cab's for you.
But again, i don't know if they will work on te Diamond!v
Click to expand...
Click to collapse
I'm a little leary replacing the BT stack that's currently working pretty good (aside from the dropping problem) unless I can assure myself that I can re-install it if the new one doesn't work.
Oh and let me say MusicMaster, you've been very helpful so far. Thanks.
TheMusicMaster said:
The BT toggle app does nothing more than redirect the audio to the next available (connected) device. I use it switch to earpiece, when i answered the phone with the buttons on the Diamond (when i answer calls with the button on the earpiece, it does that automatically).
When listening to music, i can switch the audio between the earpiece and the car stereo.
So i figured, maybe you could use it in the same way, when you walk to the car enjoy the music trough your headset, and when you are in your car, click whatever button it is on your Rokr that activates the connection and simply click the icon to change the audio from your headset to the Rokr.
Click to expand...
Click to collapse
I don't think this will work this way for me. From what I could see the Rokr will not pick up the BT from the HBH-DS970 until and unless I power off the HBH-DS970. Just like my second HBH-DS970 could not get the BT passed to it until the first HBH-DS970 was powered off. But I'll go and check this out...
edit :
After reading your story about your Rokr again, i begin to believe there is something wrong with the BT portion in your Diamond (connection dropping, having different icons say different things about BT state). Your Rokr wants to make the connection by pressing the button, and that is how easy it should be.
That's how it works for me. I would recommend upgrading to the latest ROM, i downloaded it from the official HTC website.
I mentioned the exact filename with version number a few posts ago.
That way, you will be sure that software (BT stack) is o.k., i can confirm that in my case it does what it is supposed to...
Click to expand...
Click to collapse
I think that perhaps your situation is different. You mentioned that your "MBR-100 uses A2DP, my earpiece HFP". Yet AFAICT my HBH-DS970 uses A2DP and the Rokr also uses A2DP. Both are attempting to receive stereo music.
defaria said:
Define "different profiles" in this context...
Click to expand...
Click to collapse
I meant, e.g. if your headset used HFP and your Rokr A2DP, they could be connected at the same time. Now i read in your post they both use A2DP so the whole toggling trough different profiles solution is off the table..
defaria said:
What I'm asking is "Why not? Why this seemingly artificial limitation? Is is security concern? Did nobody think anybody might want to do this? Is it a hardware limitation? Is it a Bluetooth 2.x limitation?". It just seems silly to me to put a limitation like this for seemingly no particular reason. Ya know some people might want to actually share their music in like real time!
Click to expand...
Click to collapse
I don't know the reason behind that (share music in real time would be awesome, though) but i can think of one technical limitation, and that is bandwith.
If you set the bitrate too high you wil experience skips. When i discovered the highest possible setting without skipping, i even had to set it a bit lower because i use my earpiece simultaniously. The music played without skips, but as soon as i would turn the earpiece on it would start skipping.
It is also impossible to stream audio and transfer data via PAN. Both the connections are o.k. but te A2DP stream would stop until the data is transferred.
So i assume there would not be enough bandwith to stream audio to multiple devices..
defaria said:
But another thing that would make me go for the new ROMs is if I could get rid of the god awful Sprint Music Player (SMP or actually the HTC Audio Manager and its Today plugin)! This thing sucks! I usually use Pocket Player however the god damned SMP steals the AVRCP controls such that Pocket Player cannot get them. So I can't use Pocket Player and then have the Play/Pause button on my HBH-DS970 play or pause the SMP! You end up having two audio streams playing at the same time and the pause button does not pause Pocket Player! If there's a ROM out there that removes the silly SMP then I'm all ears!
Click to expand...
Click to collapse
Heh, i use Pocket Player as well Unfortunately i don't use AVRCP but i think that is a software issue. I've read somewhere else on this forum users having the same complaint. Did not see a solution there..
Question : is this sprint player integrated in TF3D? There is a tweak tool out there to remove tabs. I removed the music player tab.
The other solution would be to go for the updated ROM from HTC. I understand your worries concerning support after flashing but i have flashed every phone i had and had never any problems.. My (flashed) Wizard broke down once, and T-Mobile (my carrier then) repaired it without any cost..
I must say i don't know how Sprint handles these things (i live in Europe).
A good thing is it's a ROM upgrade from the official HTC website so i don't think you have to change SPL (which from what i heard, is the warranty-voiding process). But anyway the sprint player is NOT included..
defaria said:
I'm a little leary replacing the BT stack that's currently working pretty good (aside from the dropping problem) unless I can assure myself that I can re-install it if the new one doesn't work.
Click to expand...
Click to collapse
You can always perform a hard reset, the MS BT stack will be intact.. (maybe use Sprite backup before you install another stack, it works really well (i don't know if you have the program, it came with my Diamond))
defaria said:
I think that perhaps your situation is different. You mentioned that your "MBR-100 uses A2DP, my earpiece HFP". Yet AFAICT my HBH-DS970 uses A2DP and the Rokr also uses A2DP. Both are attempting to receive stereo music.
Click to expand...
Click to collapse
True, the idea of using the BT audio toggle is definately not going to work for you.
But, our situation has similarities! Like i mentioned, i use two MBR-100 devices. When one runs out of energy, i use the second one. They both use AD2P!
The process of changing the two is really simple, and i believe it should be as simple as that with your two A2DP devices.
This is how it goes wen i change the two :
- music is playing on my Diamond, sound goes to MBR100 #1.
- i power off MBR100 #1 (or it runs out of energy), A2DP connection closes, music keeps playing but now from the phone speaker.
- i power up MBR100 #2, press the button on it, it establishes A2DP connection and the music keeps playing, sound goes to MBR100 #2.
Simple as that, i don't even have to awake or touch the Diamond. Now i believe it should be possible that it is that easy for you too..
defaria said:
I usually use Pocket Player however the god damned SMP steals the AVRCP controls such that Pocket Player cannot get them. So I can't use Pocket Player and then have the Play/Pause button on my HBH-DS970 play or pause the SMP!
Click to expand...
Click to collapse
I may have found something that can help with the AVRCP problem..
LINK
Unfortunately i can't test it but it looks promising..
TheMusicMaster said:
I may have found something that can help with the AVRCP problem..
LINK
Unfortunately i can't test it but it looks promising..
Click to expand...
Click to collapse
This doesn't work. The "plugin" sounds like the plugin that even Conduit already offers for older versions of Pocket Player. And the new version of Pocket Player has this already built in. The problem is it's ineffective as something in the HTC implementation is usurping the AVRCP thing. See Bluetooth in 3.7 on Conduit's forum and AVRCP not working in PocketMusic and PocketPlayer ! here in this forum.
It may be that disabling the Sprint Music Player (really HTC Audio Manager) tab and guts will solve the problem and that may be in the HTC original ROM. I don't think you gave a direct pointer but I will research this later tonight.
Pointers to how to do a hard reset on the HTC Touch Diamond such that I can get back to the original ROM from Sprint would be appreciated (I seem to recall if you burn a ROM onto the phone then a hard reset goes off of that burned ROM not the original ROM. And no I have no backup product).
This is the link to the thread where you can download the TF3D Config program to remove the music tab.
You can perform a hard reset by pressing the vol-down key and enter button simultaniously (then power up), but you can only use this to restore the current ROM you are running to its initial state.
So you are right, you can use a hard reset to restore your Diamond to factory settings now (might be useful if you just want to experiment with other BT stacks and end up with the original BT stack not working), but if you flash your phone you can't go back to its original state unless you have that factory ROM.
But, since the ROM i mentioned comes from the official HTC site, i guess when it comes to support if you ever need it, you can always put on your innocent face and say "was i not supposed to do that?"
TheMusicMaster said:
This is the link to the thread where you can download the TF3D Config program to remove the music tab.
Click to expand...
Click to collapse
Yes, except http://forum.xda-developers.com/showthread.php?p=2852736 (page 101 post by scottsimon1979) states:
scottsimon1979 said:
I am unable to get this running on my Sprint Touch Pro. I get a message saying An unexpected error has occurred in Diamond TF3D Config.exe.
When I go to details, this is what I get:
Diamond TF3D Config.exe
NullReferenceException
at f.m()
at Diamond_TF3D_Config.frmMain.v()
at System.Windows.Forms.Form.OnLoad()
at System.Windows.Forms.Form._SetVisibleNotify()
at System.Windows.Forms.Control.set_Visible()
at System.Windows.Forms.Application.Run()
at a.a()
Any ideas?
Click to expand...
Click to collapse
To which another guy said he's having problems and if you look even further down that thread I said "Me 3!". So TF3D Config does not work for us unfortunate Sprint HTC Touch Diamond owners...
You can perform a hard reset by pressing the vol-down key and enter button simultaniously (then power up), but you can only use this to restore the current ROM you are running to its initial state.
Click to expand...
Click to collapse
Forgive me but no button is labeled "enter". Which one is the "enter" button?
So you are right, you can use a hard reset to restore your Diamond to factory settings now (might be useful if you just want to experiment with other BT stacks and end up with the original BT stack not working), but if you flash your phone you can't go back to its original state unless you have that factory ROM.
Click to expand...
Click to collapse
Yes, hence my request for the Original Sprint Factory ROM...
But, since the ROM i mentioned comes from the official HTC site, i guess when it comes to support if you ever need it, you can always put on your innocent face and say "was i not supposed to do that?"
Click to expand...
Click to collapse
You're in Europe aren't you? Things are different here in the States. Sprint doesn't take to kindly to you saying "was I not supposed to do that?". Their answer would be "of course you can't do that - your warantee is now void".
It's clear to me that the HTC phone and the Sprint branded phone are not one in the same. For one the back is different. Two, it's branded with the Sprint logo all over it! 3, it has the "Sprint Music Store", something I highly doubt a European HTC Touch Diamond would have. Forth, there is no radio! None, nada, caput! I downloaded the Radio cab and installed it - even hooked up the wired headset since it needs that for an antennae - nada. I also saw postings that Sprint's phone doesn't do radio. Now I could complain to Sprint saying the HTC site boasted of an FM radio to which I'm sure Sprint will merely say "Well that's HTC. We are not HTC. Our site and our advertising never said anything about an FM Radio". Additionally the time on the home page is different. Finally, tools such as TF3D Config tool just bombs out as noted above. No, to me it's clear the Sprint phone is not the same as the HTC Touch Diamond from HTC itself.
It's not like I haven't been downloading and installing things that obviously Sprint wouldn't like. I got things like a Transparent Clock, Remove [Sprint] Logo, Flip Clock and Advanced Config and TF3D Config. I even played with downloading the HTC Audio Manager and the HTC Audio Manager Today Plugin. All of these things were cab files that I could easily, and relatively safely install, try and uninstall should it not work correctly. I'd love to "install a new Bluetooth stack" if that were doable. But burning a whole new ROM and permanently severing any hope of "support" from Sprint - voiding the warantee... Well I guess I'm not exactly there yet but you're right - I'll probably have to end up doing that.
Still it would be nice if I could get the original Sprint ROM and the HTC ROM and play around with at least a little hope of being able to go back.
Oh, and BTW, aside from the "Volume Down and Enter while powering up" thing, I recall having some .exe that I ran on my PC that did the burning of the ROM to the phone. IIRC there was some other sequence to get it to receive the ROM. Ah yes I documented this on my blog:
Once you have a ROM you run the installation process. First you need to get your phone in "Bootloader" mode. This means, on my phone, that you hold down the power and voice record buttons at the same time while you perform a soft reset. Now here's the tricky part: The screen appears to be black but if you look really carefully you'll notice it says "Serial". You'll probably have to look at it in the light and move the phone from side to side. Why the secretly displayed with no backlight screen is beyond me.
Click to expand...
Click to collapse
What's that sequence for the HTC Touch Diamond? And do these ROMs then install to this phone in "bootloader" mode?
O.k., i didn't realize your Diamond was different from mine. I figured, if we both have the same hard and software, and it works here, it has to work for you too.. When i was with T-Mobile, i got a branded HTC Touch, but this branding was nothing else then they put their T-Mobile logo on the device, and they modified WM6 so that everything has pink icons (no wonder i flashed it whitin a week ).
But the hardware was identical to original HTC devices.
I recently moved to a less urban part of the country, where there is no T-Mobile reception so i had to switch carrier, and when i switched i got the Diamond. This new carrier was Telfort, and they didn't even brand or lock the device. The only reason i upgraded the software is because i read the performance would be better (and it is )
So i see now, your situation is really different..
defaria said:
Forgive me but no button is labeled "enter". Which one is the "enter" button?
Click to expand...
Click to collapse
It's the round button in the middle. But you can also go to => settings => system and click "clear storage".
defaria said:
But burning a whole new ROM and permanently severing any hope of "support" from Sprint - voiding the warantee... Well I guess I'm not exactly there yet but you're right - I'll probably have to end up doing that.
Click to expand...
Click to collapse
One thing you can do before you decide to flash is see at HTC's website if there is an update for your device.
Before you can download the ROM, you have to fill in the serial number from your Diamond. Then you will know if they even have an update for your device.
When you fill in the serial number you will automatically get the right update. I even got the update in my own language (i'm dutch).
defaria said:
Still it would be nice if I could get the original Sprint ROM and the HTC ROM and play around with at least a little hope of being able to go back.
Click to expand...
Click to collapse
I'll keep my eyes open.., if i ever see this ROM i'll pm you.
defaria said:
Oh, and BTW, aside from the "Volume Down and Enter while powering up" thing, I recall having some .exe that I ran on my PC that did the burning of the ROM to the phone. IIRC there was some other sequence to get it to receive the ROM. Ah yes I documented this on my blog:
What's that sequence for the HTC Touch Diamond? And do these ROMs then install to this phone in "bootloader" mode?
Click to expand...
Click to collapse
No, it's actually quite easy. It is an .exe you run from your desktop when activesync is connected. Click "next" a couple of times, wait +/- 7 mins until the progress bar reaches 100% and you're done... Nice website btw. I see you play the guitar as well
TheMusicMaster said:
But the hardware was identical to original HTC devices.
I'll probably end up just flashing to the HTC ROM. Hell most of my updates so far have been to get it to be more HTC-like as they did a nice job (and Sprint has screwed it up). I just need to get some extra spare time if you know how that is....
This new carrier was Telfort, and they didn't even brand or lock the device.
Click to expand...
Click to collapse
Sigh. Someday the cell phone industry in the US will wake up and stop with this stupid branding, tickering and locking people in! Cell phone companies! It's easy - just provide good service and you're have customers coming out of your ass! But I digress (and rant!)
Nice website btw. I see you play the guitar as well
Click to expand...
Click to collapse
Thanks. Haven't played guitar in years now. Music's not what it used to be (i.e. respected) or at least not here in the US. Again, different market...
Oh, another thing, BT related. It's been frustrating but lately when I get a call I cannot answer it with the BT headset! Looking at the phone and trying Menu: Turn Hands Free On is grayed out! Quite honestly I'm no longer used to having to hold a phone up to my ear! It's damn inconvenient! Just this weekend my sister called and I was outside detailing my car a bit listening to a radio show. I go to answer the phone and it drops the BT connection! So I'm talking to her and I cannot continue my work - my car will have to wait. So I go back inside and turn on the speaker phone to listen and talk while I fiddle with the Bluetooth settings attempting to get the damn Turn Hands Free On thing to work. I turn off BT on the phone. I turn of the BT headset I have. I turn them both one - nada. I go into Settings: Bluetooth: Device and Refresh to see if the Hands Free got toggled off. Nope. I delete the device and re-add/re-pair it. Nothing. Nothing I did would get it so that I could switch to using my BT headset so I could get back to doing my car. What causes Turn Hands Free On to gray out when BT is on and the device has Hands Free toggled on? I mean shouldn't that mean that I can use Hands Free from that device? BTW, of course, a soft reset of the phone fixes the problem but by then it's too late! It's damn frustrating. And god damn it, I ask you, how hard is it to get BT working correctly?!?
Now when I get a phone call my music stops, the BT disconnects and the phone starts ringing on the speaker. I answer it and the screen goes blank and the speaker phone kicks in. Damn this is convenient! This is exactly what I want my phone to do! It anticipates my every need! NOT!!!
(Now I know somewhere there was some setting to turn off the screen when the phone picks up but I can't find it anymore. And the dropping of the BT and instead automatically going to the speaker phone - so everybody else can hear - is just unacceptable! Really, this should not be this hard! Designers of phones and their UI's - WAKE UP! Geeze!).
Click to expand...
Click to collapse
OK, I'm fed up. I'd say that just today alone I had to turn on Bluetooth after it turning itself off like 15 times today. Just going to the grocery store whenever I hit the pause button then attempted to resume playback, BT was lost - 3 times on the less than 1/2 mile drive back to my house! The HTC ROM and no support from Sprint can't be any worse!!!
I will need to spend some time getting the ROM and then preparing properly to take this step. Usually I'd do this on the weekend but my daughter's in town for the weekend so it might be the week after. I've heard about the HTC Original ROM but are there any better ones? Remember, BT reliability is high on my list. And if I can find a ROM that allows me to remove - completely gut - the HTC Audio Manager tab so that Pocket Player can have a chance at AVRCP then I'm all ears!!!
I promise to write a full report on my experiences, hopefully documenting the problems I currently have and the hopeful solutions the new ROM will give - or just the new set of problems which is probably more likely...
This has almost gotten me to the point of writing my own Bluetooth stack though something tells me that the reason it works so badly now is probably because the Bluetooth specification is overly complicated and not very well defined...
And thanks everyone for listening to my ranting and not coming down too hard on me. I'm frustrated and sometimes vent. Thanks for understanding...
Hi everyone.
First post but long time reader.
I have an un-rooted Vivid I updated the other day through the phone dial trick. Everything went fine with the update except all my previous apps appeared except for the voice dialer. I had a shortcut set on one of the screens and the label showed up with the little android guy as the image. When I clicked on it the message said the app is no longer associated. Sure enough I went through all the apps and it was not there.
I tried to install the apk and checked off the box to allow installation of unknown apps. It appeared it was working then I got a message during the install that the it did not install. I tried a few times just to be sure.
I also noticed that I am not able to use my bluetooth ear piece to accept a call or voice dial.
Does anyone have the voice dial app working or was it left out of the update? I tried the google voice app and that doesn't work with bluetooth.
I have a message to HTC regarding this as well. If there is no solution here, I will post what they plan to do if anything.
Edit 4/2/12 see the posts on pages 3&4 for a Voice dialer that works pretty good so far in ICS. There may be others that work just as well but I'm tired of trying to find them. Until (doubtful) google or HTC fixes this issue I'll stick with I have now.
I don't have a solution, but I have the same problem.
My Blueant Q2 headset has a command to activate the phone's voice command. The phone said my phone doesn't support that feature.
That's unfortunate because I use it all the time.
Sent from my HTC PH39100 using xda premium
Over 170 views and only one response.
Does everyone else have the voice dialer like we had in GB? If so can you post the apk?
Using bluetooth without it is very difficult to say the least. It's even more distracting than just picking up the phone and talking except that's not an option in many area I travel through.
vivid x2 said:
Over 170 views and only one response.
Does everyone else have the voice dialer like we had in GB? If so can you post the apk?
Using bluetooth without it is very difficult to say the least. It's even more distracting than just picking up the phone and talking except that's not an option in many area I travel through.
Click to expand...
Click to collapse
Few to try - this was an issue with the Inspire at times too. This is an older apk and probably won't work, but backup and try.
http://forum.xda-developers.com/showthread.php?t=1005228
Some suggestions here:
http://forum.xda-developers.com/showthread.php?t=1314862
Also an app in the market called Hands-free voice dial that might work
After reading your post I tried messing with the voice dialer to see if I could help. It turns out it's not even installed on my phone and its not on the market. Voice actions are supposedly alot better and I wonder if the dialer was done away with in favor of voice actions. One problem with this is on my headset it now does nothing but beep at me when I hit the call button where as it brought up the dialer before. Also I held down search and tried to voice dial through voice actions and it couldn't pick up my voice through the headset. Right after I was messing with it I got a call and the caller could here me fine through my headset. So I dunno what the deal is. Oversight maybe? I'm fine with voice actions replacing the dialer but not if my button on my headset does nothing and i can't use my headset to use it.
Sent from my HTC PH39100 using XDA
Okay, so it was a fluke, voice actions picks up my voice now. However, my call button still doesn't activate it. I have to unlock the phone and hold down search to activate it. I can make calls through it fine however so i think that is the solution. I believe the lack of support of a voice dialer button on a headset is most likely an oversight. Sucks but I hope this at lead helps you out for now.
Sent from my HTC PH39100 using XDA
Okat HTC got back to me and here is their response. It fixed part of the issue but still no voice dialer app. I can now answer an incoming call by pushing the button on the earpiece. So far only half a fix. I'll try to find a decent dialer on the market. The google one sucks.
I can certainly help you with Bluetooth functionality on your HTC Vivid. I essentially want to clear some Bluetooth data from your phone and then see if the issue continues. First let's navigate to home>menu>settings>Bluetooth. Tap on the settings icon to the right of your Bluetooth device's name and let's select unpair.
Now let's return to settings and tap on Apps, then All. Please tap on Bluetooth share and select clear data and confirm. If your Bluetooth headset has an option to clear its partnerships, please do that as well.
We need to restart the phone. To do this let's just hold down power and select restart. When the phone boots back up are you able to pair with and properly use your Bluetooth headset?
yeah I can answer calls, and if I hold it down, it'll redial the last caller in my call log. But yeah if i just hit the button, it makes a beep and does nothing. I actually primarily use my headset for music playback, its a motorola SD-9 stereo bluetooth headset, but it works for calls too. I had to re pair it after the ICS update.
Ours do the same thing. Thanks for confirming I'm not nuts. I hope they didn't rush the update through just to be first with the update to ICS.
I have an older Moto HS850. I'm searching for a decent visor set since I now wear hearing aids. It's a bit tough to hear with the BT earpiece as it is since I have to have an aid out. Until I can get a decent voice dialer app I'll hold off on blowing money for a half assed solution.
Hope HTC comes through and develops a dialer for ICS. At least you'd know it'll be functional. So far I've tried three apps off the market and none have worked for what I need.
I guess I can always switch my phone out with my daughter if I really need to. I told her not to update yet since I was willing to be the guinea pig. She never uses her voice dialer. I would feel like taking a step back but GB was not bad at all.
I agree, gingerbread was great, I was hesistant to update but figured might as well. Hopefully HTC issues a fix for this problem quickly.
Cor-master said:
...Voice actions are supposedly alot better and I wonder if the dialer was done away with in favor of voice actions. One problem with this is on my headset it now does nothing but beep
Click to expand...
Click to collapse
I tried holding down the Search to activate Voice Actions. The Vivid seemed to use my Blueant Q2 mic. However, Voice Actions definitely doesn't work as well as the Voice Dialer for dialing contacts.
I'll be monitoring this thread for solutions.
I found a solution that isn't completely eligant buy works.
I downloaded Vlingo and setup the un-car option to auto listen for commands. Don't leave Vlingo in-car on fulltime else it will drain your battery.
However, when I signal phone commands from my header, it fires up Vlingo. Set it to default to in-car Vlingo. From the you can say "Hey Vlingo..." and speak your command. My Blueant Q2 headset still says "Feature not available" but it works.
Sent from my HTC PH39100 using xda premium
willgill said:
I found a solution that isn't completely eligant buy works.
I downloaded Vlingo and setup the un-car option to auto listen for commands. Don't leave Vlingo in-car on fulltime else it will drain your battery.
However, when I signal phone commands from my header, it fires up Vlingo. Set it to default to in-car Vlingo. From the you can say "Hey Vlingo..." and speak your command. My Blueant Q2 headset still says "Feature not available" but it works.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Vlingo virtual assistant is the best.
Thanks fro the recommendation for vlingo. I haven't tried that one yet. Seems cummbersome to use. The voice dialer app was so easy to use. Everything else so far takes too many steps.
I'm checking out the new Motorola Roadster2. There is a Moto app that is made to use for it. So far all the reviews I read did not say anything about it working with ICS or not working. Most of the gripes were from Iphone users. I may hold off a little while until such reviews start coming in.
The Voice Dialer app we had in GB was an Android app built into GB. I had a version from 2.3.4 on my retired Sony phone that I bluetoothed over to my Vivid. It installed but would not work prpoperly. I tried disabling the voice thingy from ICS and it still didn't work. When I had the GB VD installed ICS was sluggish so I removed it.
Here is the latest response from HTC:
We apologize that you are unable to use the handsfree dialing over Bluetooth. Unfortunately, the Voice Dialer app was removed with the Ice Cream Sandwich update. There is no information available as to when or if this will be added again on the device as it was a change made by Google.
This might fix it,
I took the Bluetooth.apk from a Cyanogenmod and it got my wiimote to connect (see my post: http://forum.xda-developers.com/showthread.php?t=1560647) it should lift any nasty restrictions that HTC's bluetooth version has put on anything.
zacgoesrawr said:
This might fix it,
I took the Bluetooth.apk from a Cyanogenmod and it got my wiimote to connect (see my post: http://forum.xda-developers.com/showthread.php?t=1560647) it should lift any nasty restrictions that HTC's bluetooth version has put on anything.
Click to expand...
Click to collapse
My issue isn't being able to pair my device it has to do with an app that Android left out of ICS that worked so well in GB.
Thanks for the info though. What can you do with the Vivid when it's paired with a wiimote?
vivid x2 said:
Thanks fro the recommendation for vlingo. I haven't tried that one yet. Seems cummbersome to use. The voice dialer app was so easy to use. Everything else so far takes too many steps.
Click to expand...
Click to collapse
I understand vivid x2. I had used Vlingo before but then switched to the native Voice Dialer for the simplicity.
My problem with most 3rd party voice dialers is the only recognize and expect first names. With over 600 contacts, that won't work for me. Vlingo and Voice Dialer did use first and last names.
Sent from my HTC PH39100 using xda premium
Im having another bluetooth related issue. I primarily use my headset for listening to music. Since the ics update my music will go into random skipping sessions. It's not related to 4g or wifi as I mowed my lawn using a regular set of headphones and didn't have any issues. There is almost a pattern to the skipping actually. If kill pandora or Google Music and restart it'll fix the issue for a little bit but it'll start up again eventually. No issues before the update.
Sent from my HTC PH39100 using XDA
Bluetooth Hands-Free Dialing Broken
After reading this thread, I tested my bluetooth hands-free connection in my car. It's BROKEN. My Vivid will connect to the car's audio system via BT, but it will not recognize my voice requests to call a number. It was working last week before I did the ICS "upgrade."
I expected something to not work, but I didn't expect something as critical as a safety feature. I use the hands-free dialing for obvious safety reasons. I have a feeling that HTC is catching heck about this one. They are about to catch some more from me.
I hope this isn't a case of "you got your update now shutup". Hopefully they'll release an update for bluetooth and voice dialing
Sent from my HTC PH39100 using XDA
I didn't want to bog down any of the various ROM threads with this, but I've noticed some odd behavior when pairing my D4 to my JVC head unit.
With stock Moto ICS and Eclipse 1.3.2 (still ICS), when paired to the HU, I can voice dial and control Pandora. I can sort-of control Google Music, but it won't display the ID3 tag info for any of the music, and although I can skip tracks it never recognizes anything but the player being stopped.
Now, if I go to Hashcode's WIP unofficial CM10 port, the HU control of GMusic works completely (as does all the Pandora control). I get ID3 tags, it recognizes when the player is stopped, playing, paused, etc. Of course, the current state of the CM10 port has the same BT issues with the phone side of things that the D3 had early in its development.
So now I'm wondering why there's the difference with the GMusic control/ID3 info. Does anyone know if it's something in the ICS/JB framework, or is it something related to the BT stack? Or perhaps something else entirely?
edit: So it turns out stock ROMs from pretty much every manufacturer (maybe all of them) do not support AVRCP 1.3+, but CyanogenMod does. I'm currently loading Hashcode's stock CM9 to see how it fares.
edit 2: Apparently CM9 has the same BT phone issues as CM10, I hadn't realized that. I guess I'm stuck with stock/Eclipse with no tag info until CM10 matures a bit more.
It is amazing just how many problems that this Droid 4 has when it comes to Bluetooth, and everything else. I don't understand how they could release these phones with so many issues. I see it more of a false advertising deal that just goes unchecked. I have major issues with bluetooth, if I get call waiting it resets my bluetooth connection (to where I hear my BT headset replay its boot up music). Half the time I have to pair the headset, then turn off the BT section and then turn it on again just for it to work. I am also constantly repairing the headsets as well. My two motorcycle headsets also also not happy and do not play well with the Droid 4. These headsets all seem to work fine with my older phones, T-Mobile G1, G2, G2x, and my Acer Iconia A500 tablet as well.
Here are my Headsets:
Jawbone Icon(Current Edition sold at Costco)
Parrot SK4000
Cardo Scala Rider FM
Not sure if my list helps any with research going forward, but it is something.
Tom
Yeah, BT performance is all over the place between Moto-stock, stock-ish Eclipse/mybearfish, and CM9/10.
I noticed while driving around today that in addition to everything I mentioned already, Moto-stock will tell the head unit when I get a text message, but stock-ish Eclipse/mybearfish doesn't. IIRC CM10 wouldn't do it either, but that's not all that surprising given its alpha state now.
I'm at a point now where I might finally be willing to give up the HW keyboard and just get a GNex in a month or two after Google announces whatever the hell is going on with the next Nexus phone(s).
Eh, BT works flawlessly for me. If you aren't stock, you shouldn't complain about BT because it probably isn't Motorola's fault.
If you are stock, that try a factory reset (sorry ), and if it still doesn't work, get a replacement 'cause your stuff is broken (just make sure it isn't your headset first!)
Except it doesn't work "flawlessly" because Motorola didn't put in support for anything newer than AVRCP 1.0. No amount of resets and replacements will change that.
I've only rooted, so it is not that big of a deal. Still is it that hard to upgrade that bluetooth section to something newer? This was supposed to be their latest hardware keyboard phone.
Sent from my DROID4 using xda app-developers app
This is such a simple problem..
I tried explaining this to HTC tech support but they only have AT&T phones to look at and hold when customers call in.
The AT&T HTC One (M7) phone uses a custom setup for its car dock mode.
I am asking anyone who does NOT have the AT&T version to do a simple car dock mode test.
Here is the problem:
In Car Dock mode (whether you launch it via the app drawer or you plug it in to the official dock which launches it for you) in the bottom right corner is the SPEAK icon.
Launching SPEAK will enable you to call someone or search for music by voice (simple) it also has confirmation though unlike Google Voice Dialer or Google Voice Search.
(there is no icon in the App Drawer) it is only accessible in CAR Mode.
The problem is when you launch it, by design it searches through your contacts and music for just a few seconds to check if you have new contacts or music since the last time you launched it and becomes aware of them. So when opening SPEAK it says on the screen:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
(it also says audibly via the speakers "PLEASE WAIT" (again, not the exact wording but close enough)
Then when its done searching (about 1 - 3 seconds) it makes a tone and starts listening for your commands.
This works perfect and its a great feature when driving.
NOW HERE IS THE PROBLEM I NEED TESTED:
When a bluetooth device is connected it will hang on the screen where it says:
"PLEASE WAIT A FEW SECONDS WHILE UPDATING CONTACTS AND MUSIC".. (not the exact wording but close enough)
At this point you should hear "PLEASE WAIT" (again, not the exact wording but close enough) but that NEVER happens, it just hangs there until you disconnect the bluetooth device and then reconnect it. Upon the bluetooth device reconnecting it finishes searching and works without any problems.
NOW PLEASE READ THIS CAREFULLY..
It works with a bluetooth car stereo, headset, etc just fine if you launch the SPEAK app from the Car Dock icon. All is spoken through the bluetooth device and all is perfect like you would expect.
Its ONLY when launching it via your bluetooth button that it hangs.
So the audio stream is working either way, but its the initialization from the bluetooth device that causes the hang..
THIS IS SO SIMPLE TO TEST FOR ANYONE WITH A BLUETOOTH CAR STEREO, HEADSET, ETC. EXCEPT FOR HTC BECAUSE THEY ONLY HAVE THE STUPID AT&T VERSION AT HTC TECH SUPPORT (argh!)
I managed to get it to work back to back successfully only once but I can not get it to do it again.
IF I can get a few people to verify this flaw we can get a fix started via HTC.
I tried to report the problem to them but they can not see what I am talking about so directing them to this forum after others verify it might just make the difference.
Any and all help is very appreciated, thanks...
Really???
143 views and nobody can take a second to test this with their bluetooth accessory?
so sad...
IIHomieII said:
Really???
143 views and nobody can take a second to test this with their bluetooth accessory?
so sad...
Click to expand...
Click to collapse
Well, I don't use BT devices, but I have one here somewhere.
I will try to recreate the conditions you specified. I can only do it tomorrow though.
Anyway, did you try that with other BT devices?
xineis said:
Well, I don't use BT devices, but I have one here somewhere.
I will try to recreate the conditions you specified. I can only do it tomorrow though.
Anyway, did you try that with other BT devices?
Click to expand...
Click to collapse
Yes, it clearly states above that I have tried it with 2 earpieces and a bluetooth Stereo for a total of 3 devices.
This is why I need some other results from other HTC One owners with a bluetooth.
IIHomieII said:
Yes, it clearly states above that I have tried it with 2 earpieces and a bluetooth Stereo for a total of 3 devices.
This is why I need some other results from other HTC One owners with a bluetooth.
Click to expand...
Click to collapse
Sorry, I must have missed that. The only thing I found was "bluetooth car stereo, headset, etc".
Anyways, I found the earpiece but it needs to be charged. I will test it as soon as it has enough charge.
xineis said:
Sorry, I must have missed that. The only thing I found was "bluetooth car stereo, headset, etc".
Anyways, I found the earpiece but it needs to be charged. I will test it as soon as it has enough charge.
Click to expand...
Click to collapse
Anxiously awaiting your results.. and thank you
IIHomieII said:
Anxiously awaiting your results.. and thank you
Click to expand...
Click to collapse
Well, I did it. And it seems you are right!
When I try to launch the Speaker app (in Car mode, obviously) it hangs at "Just one moment, preparing your contacts and music now".
I don't even get to hear the "Please wait a moment".
If the app is launched from the phone itself it works as designed. So, bug confirmed.
Unfortunately, I could only test that with one old BT car stereo, as I couldn't connect the One to the earpiece I have.
xineis said:
Well, I did it. And it seems you are right!
When I try to launch the Speaker app (in Car mode, obviously) it hangs at "Just one moment, preparing your contacts and music now".
I don't even get to hear the "Please wait a moment".
If the app is launched from the phone itself it works as designed. So, bug confirmed.
Unfortunately, I could only test that with one old BT car stereo, as I couldn't connect the One to the earpiece I have.
Click to expand...
Click to collapse
Thank you for taking the time to test this.
I did not get a lot of responses but you have confirmed for me that it will do no good to return this to T-Mobile just to get another one with the same design flaw.
I know the international versions of the HTC One (M7) are basically the same as the T-Mobile version minus the additional T-Mobile software.
The international version has been upgraded from 1.27 (that is T-Mobile) to 1.28 and now 1.29.
They have claimed in version 1.29 better bluetooth device recognition. (whatever that means)
So if I can just get the version number you have, I can confirm if this is still a flaw or one that could go away with an upgrade
(whenever T-Mobile releases them)
I am hoping you are not on anything other than 1.27 and if yours is indeed a non-Carrier specific version (international) that a simple upgrade will resolve this..
IIHomieII said:
Thank you for taking the time to test this.
I did not get a lot of responses but you have confirmed for me that it will do no good to return this to T-Mobile just to get another one with the same design flaw.
I know the international versions of the HTC One (M7) are basically the same as the T-Mobile version minus the additional T-Mobile software.
The international version has been upgraded from 1.27 (that is T-Mobile) to 1.28 and now 1.29.
They have claimed in version 1.29 better bluetooth device recognition. (whatever that means)
So if I can just get the version number you have, I can confirm if this is still a flaw or one that could go away with an upgrade
(whenever T-Mobile releases them)
I am hoping you are not on anything other than 1.27 and if yours is indeed a non-Carrier specific version (international) that a simple upgrade will resolve this..
Click to expand...
Click to collapse
Mine is indeed the International version, but unfortunately with 1.29.401.12 firmware.
I would like to do more tests though. Maybe it's something we forgot to do. If anyone else could test this hypothesis, please do so!
As for the "better BT recognition", I have to say that it does find BT enabled devices very fast (although I couldn't find my old BT earpiece...).
bt fault confirmed
Just tried this with same phone and exact conditions. Can confirm same results and hanging.
xineis said:
Mine is indeed the International version, but unfortunately with 1.29.401.12 firmware.
I would like to do more tests though. Maybe it's something we forgot to do. If anyone else could test this hypothesis, please do so!
As for the "better BT recognition", I have to say that it does find BT enabled devices very fast (although I couldn't find my old BT earpiece...).
Click to expand...
Click to collapse
samuel uduperm
Same for me...
If I press the steering wheel button in my car to open a voice command, it hangs. If I press the 'Speak' button on-screen, it doesn't hang.
Software number 1.28.771.6
This is an Android problem I believe. Google now voice search doesn't work when I am connected to blutooth in my car on any phone I have ever used.
So I didn't expect HTC speak to work either.
Sorry gunnyman but you've got it wrong, I am currently able to use Google Voice search just fine and I've always used Google Voice with numerous Bluetooth headsets & car stereos however this HTC Speak problem is exactly that, its the app itself that needs to be updated to work properly through bluetooth.
As for your Google search bluetooth problem, not sure why you're having that issue but it definitely works just fine. On the HTC One I have my JVC car stereo forward track button set for a long press to start Google voice search and I use it all the time in the car.
I have had several Android phones with Google Voice Search and its always worked for me whether its a custom ROM or the stock phone all the way back to the original G1. We can always use voice search.. maybe not voice search over Bluetooth since that was not available until later versions of Android.. but once it was added it works great, not voice dialing ( that still sucks ) but the Google voice search/actions portion. G1, MyTouch 4g, Galaxy S, G2x, HTC DNA, HTC One etc..
Hi,
I've bought a "Jabra Stealth" headset and I'm unable to launch Google Now on my Nexus 6 (Android stock 5.0.1, FrancoKernel r8) with the dedicated button although it's a built-in feature of the headset. I assume that this is an issue of compatibility with Android 5.0. Jabra has answered me that I didn't configure vocal commands well but that's false. Has someone encountered the same problem and has a solution for it?
Thanks
xof9999 said:
Hi,
I've bought a "Jabra Stealth" headset and I'm unable to launch Google Now on my Nexus 6 (Android stock 5.0.1, FrancoKernel r8) with the dedicated button although it's a built-in feature of the headset. I assume that this is an issue of compatibility with Android 5.0. Jabra has answered me that I didn't configure vocal commands well but that's false. Has someone encountered the same problem and has a solution for it?
Thanks
Click to expand...
Click to collapse
I have a similar issue. I use a Plantronics Voyager Legend. A couple of issues:
1) press and hold of the action button will bring up "voice dialer" instead of "google now". I dont know if you've ever tried to use voice dialer, but i think its more or less deprecated since the nexus 1 was the new kid on the block.
There is an app for bluetooth on the app store that lets you choose what to launch with that button. however, it didnt work that well for me. lots of lag and it blended together with other bluetooth related issues.
2) Bluetooth never seems to "turn off". I have a smart sensor enabled headset. IE the phone should know if i have the headset on or not, and pipe phone calls and notifications and ringtones to the speaker if i dont have it on and to the headset if i do. instead, the phone constantly pipes EVERYTHING to the bluetooth headset. no fix yet.
3) phone connection to my car's bluetooth makes my audiobook start playing. I have no idea why. it is not a setting in the audiobook app. Seems that the fix is to disable streaming media over bluetooth (contacts/messages only)
From what ive witnessed with issues regarding audio, screen brightness, bluetooth, this is yet another half-baked google product with little to no attempt at a proper follow through. just a crap device rushed to market with tons of potential and a complete crap OS and barely any thought or usability effort put into anything except the home screen.
I also have the N6 with the P Legend. I am having issues where the caller can barely hear me. Do you know if you have this issue at all?
shrimants said:
I have a similar issue. I use a Plantronics Voyager Legend. A couple of issues:
1) press and hold of the action button will bring up "voice dialer" instead of "google now". I dont know if you've ever tried to use voice dialer, but i think its more or less deprecated since the nexus 1 was the new kid on the block.
There is an app for bluetooth on the app store that lets you choose what to launch with that button. however, it didnt work that well for me. lots of lag and it blended together with other bluetooth related issues.
2) Bluetooth never seems to "turn off". I have a smart sensor enabled headset. IE the phone should know if i have the headset on or not, and pipe phone calls and notifications and ringtones to the speaker if i dont have it on and to the headset if i do. instead, the phone constantly pipes EVERYTHING to the bluetooth headset. no fix yet.
3) phone connection to my car's bluetooth makes my audiobook start playing. I have no idea why. it is not a setting in the audiobook app. Seems that the fix is to disable streaming media over bluetooth (contacts/messages only)
From what ive witnessed with issues regarding audio, screen brightness, bluetooth, this is yet another half-baked google product with little to no attempt at a proper follow through. just a crap device rushed to market with tons of potential and a complete crap OS and barely any thought or usability effort put into anything except the home screen.
Click to expand...
Click to collapse
When the caller can barely hear you, check your phone. Sometimes, even though my headset is on, the phone doesn't care and attempts to use the phones speaker or mic.
shrimants said:
When the caller can barely hear you, check your phone. Sometimes, even though my headset is on, the phone doesn't care and attempts to use the phones speaker or mic.
Click to expand...
Click to collapse
That's my current issue...
I can answer the calls with either my truck or ear piece, but both will randomly not have audio. The phone says it's connected BT, but I have to switch the source to speaker or handset and then click back over to BT. The whole time while I'm begging the person on the other end not to hang up and to hold on a second. Not bad when I'm at my desk with earpiece....let's just say it's a bit more nerve-racking on the highway.
scap99 said:
That's my current issue...
I can answer the calls with either my truck or ear piece, but both will randomly not have audio. The phone says it's connected BT, but I have to switch the source to speaker or handset and then click back over to BT. The whole time while I'm begging the person on the other end not to hang up and to hold on a second. Not bad when I'm at my desk with earpiece....let's just say it's a bit more nerve-racking on the highway.
Click to expand...
Click to collapse
Same here. Also have a problem where, when on a call, an incoming call will kill bluetooth. This makes it unusable in my car as it becomes a real safety issue. I have to turn off BT and use the speakerphone which luckily is good enough for the job. Even switching the source and switching back doesn't always work for me.
I regret not sending the phone back for this problem. I'm waiting on v5.1 this month as rumored, hoping that will solve the problem. May just go back to my Lumina 925.
Has anyone tried going into Google settings app -> Search & Now -> Voice and turn on Bluetooth Headset (records audion through bluetooth headset if available).
I have Nexus 5 and Jabra Stealth and I had the same problem. I could solve it thanks to these indications: hackerspace.kinja.com/reassign-your-bluetooth-phone-button-to-open-google-n-1507391132
Same issue with calls not having audio through the car Bluetooth unless I switch to speaker/handset then back. I guess Marshmellow really messed up Bluetooth on a lot of people's phones not just us. Tried different rooms(AOSP, CM, stock) no help even tried updating the radio which helped Bluetooth crashing completely and requiring a restart but the phone issues remain.