Related
first i bought a sim-free kaiser - had problems getting bluetooth to work when wifi was connected - got so pissed off with it i sent the unit back - now ive got another unit (a vario 3 this time) and i am having the exact same bloody problem - what the hell is going on? cant this device do bluetooth and wifi at the same time? i want to stream music over wifi to my BT stereo headset FGS
Any equipment wether it is a phone, laptop or PC will have somewhere in its manual that recommends WiFi and Bluetooth are not used together. Both systems run on very close frequencies and cause interference to each other.
The problem is enhanced by the proximity of the Tx and Rx of each system within such a small unit as a phone or PDA.
I wanted to do the same as you and found BT falling off due to the high rate of packet retries on each so reverted to wired headphones.
Add a cellphone TX and Rx to this also and you have one NOISEY set of close by systems.
i have heard reports of people using both together in harmony on the kaiser - and a lot of people who own other devices (ie htc universal, sony ericson, p990i etc) do not seem to have this problem
i appreciate that bluetooth and wifi share the same frequency bandwidth and this will inevitably cause packet loss - but not nuke it all together! afaik bluetooth hops 1600 times a second (or smt like that) all over the spectrum, where as wifi tends to stay within a certain band?
Lately, I've had a little trouble with using WiFi with A2DP on my Jabra BT8010. Periodically, I get dropouts on the sound, which seem to be associated with WiFi disconnects -- I lose the WiFi momentarily, then as it tries to re-connect to the AP, I lose sound. Not a range issue -- this happens even when I'm right on top of the AP.
I haven't had any problems with WiFi & BT in handsfree or HID modes, just A2DP.
guess im just really unlucky :/
3waygeek said:
I haven't had any problems with WiFi & BT in handsfree or HID modes, just A2DP.
Click to expand...
Click to collapse
A2DP uses 200-400 kbps, while handsfree / HID only a fraction of it.
fusi said:
guess im just really unlucky :/
Click to expand...
Click to collapse
You're not alone. There are 5 reports of this in the HTC Wiki, and I've run into it myself. If I'm using wifi and I answer a call with my bluetooth headset, WiFi simply stops working. Likewise, if I'm using the headset and I try to switch on WiFi, the device can see the network, but can't connect and will eventually drop the network configuration and prompt me for the WPA passphrase.
Edit: I tried upgrading to the 1.27.12.17 radio ROM, but no joy.
I'm having the same problem, but I'm using the ROM that the Kaiser came with. Has anyone tried using Dutty's ROM or something?
Maxim726X said:
I'm having the same problem, but I'm using the ROM that the Kaiser came with. Has anyone tried using Dutty's ROM or something?
Click to expand...
Click to collapse
Do us all a favor and give HTC a call and report the problem. I have nothing against the cooked ROMs, but just like the video drivers, it would be nice if there was something official from HTC:
+1 866 449 8358
Just wanted to say that I too have the same Bluetooth + Wifi problem. When I have Wifi on, it's nearly impossible for me to connect to my PC with a Bluetooth connection. I have only had some luck when I established the bluetooth connection and then turn on Wifi.
HTC says they're trying to reproduce the issue and will get back to me in the next day or two. Again, I strongly encourage you to give them a call.
sinanju said:
Do us all a favor and give HTC a call and report the problem. I have nothing against the cooked ROMs, but just like the video drivers, it would be nice if there was something official from HTC:
+1 866 449 8358
Click to expand...
Click to collapse
Just called them, and the woman on the phone basically told me not to expect any updates within the next few months, if ever. What the hell is that about? To that I responded 'so basically you're saying that you don't support the device'... She kind of dodged the question, but it seems to be that way. We're kinda on our own... Which is unfair, but this verification removes any remorse I would have about hacking the **** out of my phone. So now that it is verified that we're being hung out to dry, do any of the ROMs address this issue?
As will all other customer service organizations, if you don't like the answer, call back.
Getting them to reproduce and recognize the issue is the first battle.
Smart Answer mate. I have an SDA and haven't noticed that problem so far, I'll try to see if its been happening un noticed. Anyone know where i can find A2DP profile for the SDAII ?
Maxim726X said:
I'm having the same problem, but I'm using the ROM that the Kaiser came with. Has anyone tried using Dutty's ROM or something?
Click to expand...
Click to collapse
Im using Dutty's ROM and have the same problem.
Has this issue been resolved with the new Firmware, to anyone's knowledge?
The recently released AT&T ROM does not fix the issue. Support told me they have sent a report back to engineering. I'm going to give them 'til the end of the week before I call them back.
Any Updates or fix regarding Wifi and Bluetooth interference on the HTC?
Let me add to my own finding...
I have 3 laptops and 1 PC that is on the WiFi. If my HTC Kaiser craps out using the Wifi with bluetooth. It takes the WHOLE entire Wifi network down( for about 30sec to 1min). I can see all my laptops and PC dropping Wifi and trying to reconnect.
Hello all,
First off, I am a noob here, so i expect I may say something stupid. Thank you for your kindness, if you wish to correct me. I'm having an issue with the Diamond - it completely freezes when I attempt VOIP calls. Only solution is to take out the battery. No gray screen, no warning, just frozen. I suspect a HW issue, maybe the WiFi.
Originally I was using Morna ROM 1.7.1 which worked well. VOIP was choppy though - not enough RAM in my opinion - so I tried some lighter ROMs. The problem started while I was changing ROMs, and now it's persistent regardless of ROM. I've tried various versions of Morna, Duttys, Tom's, Energy, Nataly... then back to the original, still the same problem.
The crash doesn't always occur at the same spot. Sometimes it's while placing a call, sometimes while on the call, even while configuring the SIP client. I've used different clients, incl Skype, SJPhone, Fring, PortSIP... I suspect it might be a WiFi issue, because I saw the connection drop/reconnect a few times while in a call, before crashing. That said, browsing through WiFi is no problem.
Did I fry some hardware with the repeated re-flashing? Please help! I'm not sure if there are any debugging tools/methods I can use here to better understand what's happening. I've decided to use this phone only at home for VOIP calls (no mobile), so I need to solve this issue.
Try using AGEphone, best softphone that I have found. It will also put all calls through the main speaker, a major problem with most softphone clients on HTC devices.
I have a samsung gt i7500 but I'm sure the problem is android related.
After playing around with some roms and one time when I called someone he did not hear me and I didn't hear him, it worked only with the microphone and the headphones it came with. From there on reinstalled all possible roms versions and default versions and I always have the same problem.
Also I noticed that if I try to play music on the speakers I can't hear it.
Today I installed a new rom and saw the music DID work before making a call. But after the call with no voice/sound the speakers music didnt work any more either.
At one samsung shop a guy told me that he can't fix it but the internal drivers/software components are of different versions.
I think it might be the phone.tar file with an amss file inside that is ****ed up.
Any ideas? hoping someone can help
I don't know why are you making assumptions out of nowhere ("Android related"?), why you're blaming the OS for your messing with ROMs (everything worked before, didn't it?), and why are you posting on Nexus forum, when someone from Samsung forums would have much higher chances of knowing something about this problem.
Other than that - supposing that i7500 is like other current high end phones and has separate baseband CPU and apps CPU, I suppose you're running a corrupted / wrong radio build.
How can I check the radio built?
Settings => About
Look at the baseband version.
jump on irc... chat.freenode.net
#i7500
We'll help you
oo nice chan! imma hit that up!
cool
lots of custom roms and even a asop android 2.1 beta
Well i've been doing a bunch of stuff to my phone to get things humming along, but the one thing that hasn't worked at all is Bluetooth Voice Command Dialer.
I've tried the native bluetooth voice command dialer, and the following apps below:
Vlingo Virtual Assistant
Choice Dialer
Bow Tie
The bluetooth handsfree that i am using is the Samsung WEP200 and I own 3 of them and all 3 of them don't work.
When i mean don't work, i hit the command button and it would prompt with the "Bluetooth Voice Dialler" prompt and I try to speak but nothing is happening. The audio routes to the bluetooth, but i suspect the mic isn't.
Bluetooth calls and call last caller works, but that is it as it is basic bluetooth capabilities.
So at the moment I am stumped and wondering if anyone out there got it to work and what your handsfree is.
I have noticed the same problem. Is your phone a Rogers Captivate using Kies to update or it's an ATT Captivate using Odin to flash rom?
I have i897 AT&T and Odin flash and I notice this issue. When I was on the Rogers ROM 2.1, my bluetooth wouldn't pair. Now on 2.2, I can pair and call using BT, but voice dialler doesn't seem to have the mic on...
I tried bluetooth mic tester app and it didn't record anything via bluetooth.
I'm using the Rogers Froyo over Kies. It took me forever to install it since i had to repair my nv_data.bin.
This problem plagued me from Cognition 2.3b8 as well. To date I haven't had a Froyo install that worked with Bluetooth Voice Command Dialer.
If anyone out there that had the bluetooth voice command dialer to work on their captivate I'm all ears. I am thinking maybe it is because my Samsung WEP-200 is too old?
BTW, I'm using Jawbone Prime.
I also tried other apps vlingo and all those none seem to be able to capture mic from BT when voice dialing. I can have voice conversations using my BT, but no voice dial.
Well I think it might be a general issue with Froyo and Samsung Captivate in general, regardless of Froyo custom builds. If someone else has it working on a specific ROM i am all ears.
Later tomorrow I will contact Samsung Support and ask them about this, because this is really stupid.
Just wonderful. Well, I hope that's not your true official Froyo. If so, Samsung is just killing me. I've been running I9000 Froyo ROMs because the first nor second Cappy Froyo leaks don't have this functionality. This is the one function I want Froyo for more than anything else. I hate to say this, but my iPhone 3GS worked perfectly (you know what that means: I could voice dial over Bluetooth, but the call wouldn't stay connected!!). I just hope this is not an indication that Froyo for Cappy - if it ever is released - will not have this functionality. It just keeps getting better with these guys.
Any updates from Samsung?
well i called samsung social hub support. Their official answer it isn't even a feature of the phone. Also they are aware that the bluetooth voice command dialer is broken on the phone and isn't supported.
I've requested they have it as a potential feature in the future as it is bylaw in some provinces and states that people use bluetooth voice command dialer.
Well this only puts one more nail in for samsung...
Also this could be related because of their stupid bluetooth stack, but there isn't much more I can find on this.
I hope this information is helpful to those looking around.
I've had it successful on two or three different ROMS. But I can't remember which for sure.
I think it worked on one of the Perception ROMS; It doesn't come on Assonance ROMS.
Something that I have done on ROMS that don't come with the Voice Dialer, I use Blue Tooth LAunche. I'm using it now on Assonance 5.2 You can configure it for what you want it to connect to.
It may take a bit of experimentation on how to configure it. When you go into the list of apps to configure, it lists all the various activities of the apps, and you need to select the right one. For example, to bring up Google Voice Search, I have it using com.google.androd.voicesearch.recognitionactivity.
Google Voice Dial
I had the same issues on Assonance 5.2. What I did was take the voicedialer.apk from Perception 9.5 and installed - that worked for me.
I have attached the apk for you, I can't for the life of me remember how I had to install it though.
I had a lot of dropped calls on Assonance and didn't realize at the time that I could just update the modem - live and learn I guess.
I just downloaded the voice dialer.
I actually have it at home, but not sure if same version. I tried to install it on one of the ROMS (I think Assonance) and was unsuccessful. I probably tried using Root Explorer. I don't think I tried just dropping it in the Apps folder. But not sure.
I'm installing Cognition 3 as I write this. We'll see how things go on that.
baxster said:
I had the same issues on Assonance 5.2. What I did was take the voicedialer.apk from Perception 9.5 and installed - that worked for me.
I have attached the apk for you, I can't for the life of me remember how I had to install it though.
I had a lot of dropped calls on Assonance and didn't realize at the time that I could just update the modem - live and learn I guess.
Click to expand...
Click to collapse
I'd try this but it wont let me install over system apps lol. Anyone know how to do it? BT dialing doesn't work on my rogers 2.2 either.
Well the bluetooth launch + vlingo voice works (the one from samsungs apps)
I've tried updating the voice dialer.apk from this thread, and this one:
http://forum.xda-developers.com/showthread.php?t=780687
http://forum.xda-developers.com/showthread.php?t=908492
No luck.
I think if we wanted to use the native bluetooth voice dialer we need to update some system libraries and also the apk file. Thoughts?
kintaro said:
Well the bluetooth launch + vlingo voice works (the one from samsungs apps)
I've tried updating the voice dialer.apk from this thread, and this one:
http://forum.xda-developers.com/showthread.php?t=780687
http://forum.xda-developers.com/showthread.php?t=908492
No luck.
I think if we wanted to use the native bluetooth voice dialer we need to update some system libraries and also the apk file. Thoughts?
Click to expand...
Click to collapse
I am hopping that when the AT&T update happens we may be able to get the files we need to get the Rogers version working...
I also tried with the VoiceDialer.apk provided in this thread and no luck. Also tried the 09SEP-VoiceDialer.apk and no luck.
I do agree that there is some system libraries that need to be updated, since there are claims that 09SEP-VoiceDialer.apk worked with others.
Since we can have conversations with our bluetooth, it's not an hardware issue. It's something with software.
Same issue here with rogers captivate.. I deleted the dialer to see what happens, and the button on my headset now did nothing, but if i held it in, it would call the last number dialed. I flashed it back to factory and got my app back, and the button brought up the bluetooth dialer again, but it doesnt work. And now pressing and holding calls voice mail again.
I wish they had a settings section to assign the button presses to applications without 3rd party apps.
I hate how rogers and samsung are washing their hands of the issue. they wont take the phone back. Its illegal here to use my phone while driving. I got the phone on the 11th. I am still waiting for the accessories I bought to arrive, everything from a desk dock to car dock, spare battery.. all OEM.
If they don't get this right, I wont be buying more products from them.
I have more faith in you guys finding a solution than them.
Same problem and I think NONE of the Bluetooth mic works on Voice Command on Froyo roms for my Captive. I've tried the AT&T leaked Rom and also the Cognition 3.04, NONE of them support Bluetooth voice dialing but no problem for normal phone conversation. Now that is EXTREMELY ANNOYING!
iPhone 5 for sure! No more Android suckers!
Just wanted to pipe in that I'm in the same boat and pretty mad at sumsung/rogers for not including bluetooth voice dialing! Is this 2011 or what?
I just bought some very expensive bluetooth headsets for my motorcycle and now find out that my brand new "state of the art" phone can't voice dial with them?
Hopefully someone figures this out. I'm counting on someone being way smarter than I am with this stuff
Man, after having this phone for 6 weeks now I'm starting to wonder why I switched from my WinMo phone. For all the hype of Android and the criticism of WinMo, there are a number of things, like voice dialing over BT, that just plain worked on my HTC Tilt 2. And I'm finding that WinMo was a lot more customizable (and a lot easier to work with) than what Android allows me to do. If it weren't for the gorgeous screen and capacitive touchscreen I would go back to my Tilt 2 and sell this POS Samsung device.
Miami_Son said:
Man, after having this phone for 6 weeks now I'm starting to wonder why I switched from my WinMo phone. For all the hype of Android and the criticism of WinMo, there are a number of things, like voice dialing over BT, that just plain worked on my HTC Tilt 2. And I'm finding that WinMo was a lot more customizable (and a lot easier to work with) than what Android allows me to do. If it weren't for the gorgeous screen and capacitive touchscreen I would go back to my Tilt 2 and sell this POS Samsung device.
Click to expand...
Click to collapse
In all fairness, this is a samsung issue. Not Android.
Hey there,
I know it has been discussed partly, but with I think different aspects and details than I have. To cut it short: in about 50% of my phone calls, be it with good or bad reception, people cannot hear me speak on the phone.
The fun thing is, this cannot be connected to the internal microphone since I have it both on the normal mic as well as my bluetooth headset. No matter whether I call them or they call me. Sometimes (!) it helps to mute and re-enable the microphone on-screen, but this is not always effective. I thought this may be related to a bad combination of firmware and radio, but I recently switched to InsertCoin GE und updated both FW and radio, to no avail as regards to that matter. Furthermore, sometimes phonecalls just drop in the middle of a conversation, with no change in signal quality as far as I recognize.
Does this sound like some software thingy (and one might have a solution) or would you believe this is hardware related?
All the best in advance
Froscher
Nobody having an idea?
Froschfinger said:
Hey there,
I know it has been discussed partly, but with I think different aspects and details than I have. To cut it short: in about 50% of my phone calls, be it with good or bad reception, people cannot hear me speak on the phone.
The fun thing is, this cannot be connected to the internal microphone since I have it both on the normal mic as well as my bluetooth headset. No matter whether I call them or they call me. Sometimes (!) it helps to mute and re-enable the microphone on-screen, but this is not always effective. I thought this may be related to a bad combination of firmware and radio, but I recently switched to InsertCoin GE und updated both FW and radio, to no avail as regards to that matter. Furthermore, sometimes phonecalls just drop in the middle of a conversation, with no change in signal quality as far as I recognize.
Does this sound like some software thingy (and one might have a solution) or would you believe this is hardware related?
All the best in advance
Froscher
Click to expand...
Click to collapse
Froschfinger said:
Hey there,
I know it has been discussed partly, but with I think different aspects and details than I have. To cut it short: in about 50% of my phone calls, be it with good or bad reception, people cannot hear me speak on the phone.
The fun thing is, this cannot be connected to the internal microphone since I have it both on the normal mic as well as my bluetooth headset. No matter whether I call them or they call me. Sometimes (!) it helps to mute and re-enable the microphone on-screen, but this is not always effective. I thought this may be related to a bad combination of firmware and radio, but I recently switched to InsertCoin GE und updated both FW and radio, to no avail as regards to that matter. Furthermore, sometimes phonecalls just drop in the middle of a conversation, with no change in signal quality as far as I recognize.
Does this sound like some software thingy (and one might have a solution) or would you believe this is hardware related?
All the best in advance
Froscher
Click to expand...
Click to collapse
Hi can you tell us what exact combination of Firmware ROM Kernel etc you are using currently?
baedaa said:
Hi can you tell us what exact combination of Firmware ROM Kernel etc you are using currently?
Click to expand...
Click to collapse
Hey there,
of course, I picked InsertCoin GoogleEdition with the corresponding 3.06.1700.10 firmware that's offered as a complementary download for the ROM. No hands on the kernel, left the one coming with the ROM. Does that help ?
Best
Froscher
Froschfinger said:
Hey there,
of course, I picked InsertCoin GoogleEdition with the corresponding 3.06.1700.10 firmware that's offered as a complementary download for the ROM. No hands on the kernel, left the one coming with the ROM. Does that help ?
Best
Froscher
Click to expand...
Click to collapse
can you do a nandroid backup and try with another ROM? You could also ask in the thread of the ROM if someone got a similar problem.
I would also downgrade the firmware to the latest for HTC One (non GE). this should not be the problem but just to be sure
baedaa said:
can you do a nandroid backup and try with another ROM? You could also ask in the thread of the ROM if someone got a similar problem.
I would also downgrade the firmware to the latest for HTC One (non GE). this should not be the problem but just to be sure
Click to expand...
Click to collapse
Yeah, I think I can. But I came from a 4.2.2 ROM with the latest radio, TrickDroid 8.0 and I had the very same problems. Does it more sound like a hardware than a software issue?
Best
Froscher
Froschfinger said:
Yeah, I think I can. But I came from a 4.2.2 ROM with the latest radio, TrickDroid 8.0 and I had the very same problems. Does it more sound like a hardware than a software issue?
Best
Froscher
Click to expand...
Click to collapse
if it happens with other ROMs too it is most propably a hardware issue