I have both a ME57C and ME572CL, running 5.0.1 WW, and they exhibit the same problems with bluetooth, which seems to rule out a unit-specific problem.
1/ BT audio works fine in headphones mode (ie stereo listening only), quality wise, but fails as a headset on the audio-in front (tested with two different BT headsets, including a JABRA BT3030) : audio in comes garbled and clipping to the point of uselessness.
2/ Whenever BT is active, it seems to interfere with WiFi networking, leading to frequent drops and reduced throughput on WiFi connections (both TCP and UDP).
Other features of BT seem to work OK (file transfer, keyboard/mouse connectivity, etc) although I haven't tested those extensively.
Anyone with similar issues or clues as to fixing the problem(s) ?
Have you contacted ASUS to ask for support or at least to make a bug report?
T1beriu said:
Have you contacted ASUS to ask for support or at least to make a bug report?
Click to expand...
Click to collapse
Not yet : I'm asking here first to see if it's a non-official-yet-known issue (I couldn't find anything on the ASUS support resources), my experience being helpdesks work best when the users do their homework.
Related
hrm this isnt good - it would appear bluetooth stops working when wifi is enabled - was listening to an mp3 on bt stereo headphones and enabled wifi and it killed the conn - not only that it seems i cant use any form of bt device if wifi is enabled (not even connected) on the device - wtf?
is anyone else experiencing this?
No, I use Jawbone BT headset with all sounds out BT using BTaudio.exe then start WiFi on home LAN and watch streaming video from Slingbox.
this was the case with the titan...
eric b
do i have a faulty unit?
i don't think so. in the titan, the bluetooth and wifi antennae were the same actual unit.
eric b
you sure? remE says both work at the same time just fine for him :s
to me it seems as thought ewifi signal is overpowering the bluetooth or smt - does the bluetooth freq lie in the wifi freq range or smt? is there any way they could overlap?
both work if i have only one on at a time - can anyone confirm either way if both work at the same time for them and what equipment youre using?
I'm doing it as a type this. I'm watching 30fps video streaming at 300k over WiFi and listening to it thru a Jawbone BT headset. For sure this works fine.
I have a Hermes and it would not do this well at all, it would allow BT and 3G video streaming but not WiFi. Kaiser can handle it.
maybe you could try a differet BT headset, maybe yours suffers from inteference ( i don't know the frequencies of BT and WiFi but WiFI could be killing the connection because your headset jamms)
BT and WiFi are both spread specktrum radios operating at 2.4ghz. They are designed to co-exist and do so on Kaiser. Maybe there is a difference with Stereo vs Mono headsets, they do use different BT profiles. If I get a chance I'll try a stereo set and report back.
thanks guys - i need to make sure my unit is duff before i ssend it back for a replacement ;(
looks like my unit is gonna go back - i called htc and they said they havent heard of this issue before and are 'escalating it' - it seems that superetrader wont give me an RMA for my unit until htc have given me a reference number - is this normal procedure? seems a bit odd to me
i tested my unit some more at work today with a whole host of different bluetooth and wifi gadgets and the problem is consistently reproducable
gutted
I found a problem with my kaiser phone last night. The problem is that if I listening to music with my bluetooth headset I am not able to connect to my WiFi at the same time. This problem is specific to A2DP because my headset can be connected to my phone and I can not browse the web with WiFi. Has anyone seen this problem before? Has there ever been a resolution for it?
stevencage7 said:
I found a problem with my kaiser phone last night. The problem is that if I listening to music with my bluetooth headset I am not able to connect to my WiFi at the same time. This problem is specific to A2DP because my headset can be connected to my phone and I can not browse the web with WiFi. Has anyone seen this problem before? Has there ever been a resolution for it?
Click to expand...
Click to collapse
I've seen this too -- when using A2DP, the WiFi connection goes down & won't re-establish itself until I turn off A2DP. I haven't found a resolution yet -- not that I'm looking for one as I almost never use A2DP, and when I do, I'm in the car, where WiFi isn't too useful.
See my post here which may be a related problem. I assume you have the same new HTC ROM: http://forum.xda-developers.com/showthread.php?t=396409
I have a similar issue. If I am streaming music, from my HP media server, over wifi and using my Plantronics 590A bluetooh headphones, after each song I am asked to log back onto the network and as each song comes to an end my device starts to search for a network connection. I don't have this issue when I use wired headphones. Clearly there is an issue when both bluetooth and wifi are used at the same time. I don't know if it's hardware or software but I'm not happy about it.
akey
HTC TyTN II (Kaiser/P4550)
Rom ver: 1.82.707.0 WWE
Rom date: 11/03/07
Radio ver: 1.27.15.32
WM 6 Professional
CE OS 5.2.1620 (18125.0.4.2)
It's normal. Without going too technical, WiFi and Bluetooth operate on the same frequencies. They will live together if they're not using too much bandwidth, but if the usage is heavy there will be problems.
A BT stereo headset represents a lot of data to send and thus bandwidth usage, which means the BT will use the spectrum heavily, stepping over the Wifi. Due to the many packet losses the Wifi connection cuts.
Other way around, if Wifi is under heavy load, Bluetooth might drop.
Nothing we can do, that's what happens when you pack 2 radios operating in the same frequency band so close to each other, or even maybe sharing the same antenna which might be the case in today's phones.
It is absolutely NOT normal. The reason I know this is that VoIP over WiFi has been running almost perfectly on my TyTN II for a year, until I installed the latest ROM by HTC which broke it.
I used to get no crackle on Bluetooth calls with WiFi turned on. Now I do.
I used to get great quality VoIP. Now it is beyond unusable.
Simply, their new ROM broke it. BT and WiFi used to live in harmony, until their buggy ROM came out the other day. I think there are many users who know this, and who expect a hotfix soon.
You're talking about calls, I assume using the BT headset profile, while the other people in the thread are using A2DP wireless stereo. They're very different in terms of bandwidth.
On mine the headset with WiFi is also fine, but not A2DP. You're apparently not having the same issue than what is mentione in this thread. Yours might be due to the ROM, but the A2DP thing is more likely to be related to what I explained. I could myself experience it with several ROMS (all WM6, never tried a 6.1).
kilrah said:
It's normal. Without going too technical, WiFi and Bluetooth operate on the same frequencies. They will live together if they're not using too much bandwidth, but if the usage is heavy there will be problems.
A BT stereo headset represents a lot of data to send and thus bandwidth usage, which means the BT will use the spectrum heavily, stepping over the Wifi. Due to the many packet losses the Wifi connection cuts.
Other way around, if Wifi is under heavy load, Bluetooth might drop.
Nothing we can do, that's what happens when you pack 2 radios operating in the same frequency band so close to each other, or even maybe sharing the same antenna which might be the case in today's phones.
Click to expand...
Click to collapse
My old TyTn II worked fine with BT and WiFi on at same time - never a problem. I always had WiFi on at home for emails etc... and always have my BT headset (Plantronics 8XX mono) working as I hate holding phone to my ear and get a lot of calls.
I recently bought another TyTn II and then unlocked it using advice form this forum (many thanks to all BTW!) and installed latest HTC rom and WM6.1 etc... Now I love many aspect of the new ROM but I can't use BT and WiFi at same time.
So from my experience it MUST be the new HTC ROM software issue.
Okay, chalk me up as another victim of this Wireless + A2DP = Crap Reception. I've tried three other Radios and the effect is the same.
I was using a rom I got in about April, and I could stream music from the internet over wireless listening to it on my Pantronics 590A's over bluetooth no issues (other than battery lol). Now with a rom I got this month, I can listen to music over bluetooth no problem, surf using wireless no issue but as soon as you mix them both it's all bad. Also, I need to re-pair my headphones whenever I want A2DP, where previously I could just turn on the headphones and have them connect. Also, no headset icon in the taskbar.
It's not a CPU issue as there's no excess usage when you both have them enabled. Personally I'm going to point the finger at the bluetooth stack here.
As far as I remembered when I first purchased the ATT Tilt with my Plantronic Voyager 855 I WAS able to stream via Wifi (Winamp Remote) and use my bluetooth without a problem. It's when I started to put cooked roms in the Tilt that it stopped working correctly...
Besides, I use a Macbook Pro via Wifi only and I listen to my Itune via my Plantronic Voyager 855 everyday. If it's true about WiFi overloading Bluetooth on the frequency. Why does it work fine on the MBP?
And Finally.... to make my point...
I also have an AT&T Fuze. Works fine there. Matter affact. I'm currently connected via bluetooth to my Fuze with my Voyager 855... turned off 3G/HSPDA on the Fuze. WiFi on the Fuze using Winamp Remote to connect to my PC streaming from there. Explain that....
Has anyone fixed this problem?
I'm experiencing the same problem on my kaiser aka xda stellar. When Wifi is turned on bluetooth A2DP stereo connection is dropped.
I believe I have found an issue with the latest (stable + nightlies) cyanogen mod rom with Bluetooth headset audio, and before I go about posting to the Dev thread I wanted to get some help with understanding how or what info a need to gather.
I have a car stereo that has support for Bluetooth (both media and voice), and whilst the phone syncs to the unit and plays music just fine, when trying to place a call, all that can be heard is a loud buzzing when the call is connected (@ both ends).
The stereo is functioning correctly, and works fine for both voice and media with my SGS2 (also running cyanogen). I also have the same model stereo in another car, and the problem manifests on this unit too.
Prior to flashing cyanogen I was using other roms (both standard and mod's) and never had any issues with voice calls.
I have tried changing the baseband, and ril but this had not made any difference. I have also paired with other headsets and they work fine, so this is down to some compatibility issue with the stereo and Cyanogen's Bluetooth stack settings, I think.
Before posting this as a bug, is there anything else I should try, and if not what info do I need to gather (other than version numbers etc) to ensure I give the dev's enough info to work with?
Thanks
If it's in stable, use the issue tracker.
Just to open with this - I really like this phone and have been enjoying using it. Aside from the fairly poor WiFi range and the flaky NFC it is otherwise a really nice phone. There's just one other issue I have which is extremely frustrating:
I can't use it with my Airpods. Or at least, I can connect it but at some point the sound will crackle and cut off. If I wait it will occasionally crackle and come back on again but will cut in and out in a way that would drive anyone mad. I've tried fiddling with Bluetooth settings in developer options but it doesn't seem to make any difference. I've even tried a factory reset.
The Airpods work absolutely perfectly with every other device - no issues with the iPhone (expectedly) nor the S8, G6 or even my laptop. I can't 100% rule out a fault with the Airpods but given these facts it seems highly unlikely.
I wondered if anyone else used Airpods and had experienced issues and found a solution.
Not too interested if you've had no issues with your device, nor what you think of Airpods - I just want to see if I can get to the bottom of this, or the Nokia will have to go back.
Many thanks
Similar problem
Got a similar problem with my apt-x receiver.
Every few minutes the connection drops for a very short time.
The airpods don't support apt-x, but maybe it's the same problem.
My receiver shows a connection via apt-x, , but you can't find any apt-x support in the Nokia 8 specs.
But I had no problems with a friends portable speaker (non-apt-x).
I went back to cables
damian101 said:
Got a similar problem with my apt-x receiver.
Every few minutes the connection drops for a very short time.
The airpods don't support apt-x, but maybe it's the same problem.
My receiver shows a connection via apt-x, , but you can't find any apt-x support in the Nokia 8 specs.
But I had no problems with a friends portable speaker (non-apt-x).
I went back to cables
Click to expand...
Click to collapse
I’m wondering if the Nokia 8 just has rubbish connectivity, generally. If the Bluetooth chip is part of the WiFi chip then this would figure as it has the worst WiFi connectivity I’ve seen in recent years
Are you running Nougat or Oreo? From what I've heard, a lot of the bluetooth issues have been fixed in Oreo.
leoni1980 said:
Just to open with this - I really like this phone and have been enjoying using it. Aside from the fairly poor WiFi range and the flaky NFC it is otherwise a really nice phone. There's just one other issue I have which is extremely frustrating:
I can't use it with my Airpods. Or at least, I can connect it but at some point the sound will crackle and cut off. If I wait it will occasionally crackle and come back on again but will cut in and out in a way that would drive anyone mad. I've tried fiddling with Bluetooth settings in developer options but it doesn't seem to make any difference. I've even tried a factory reset.
The Airpods work absolutely perfectly with every other device - no issues with the iPhone (expectedly) nor the S8, G6 or even my laptop. I can't 100% rule out a fault with the Airpods but given these facts it seems highly unlikely.
I wondered if anyone else used Airpods and had experienced issues and found a solution.
Not too interested if you've had no issues with your device, nor what you think of Airpods - I just want to see if I can get to the bottom of this, or the Nokia will have to go back.
Many thanks
Click to expand...
Click to collapse
I wonder if yours is wonky, my Wi-Fi is excellent and i get get 75Mbit down 19Mbit up over 5Ghz through 2 brick walls, a floor up and at the opposite end of the house, i have not missed any payments using contactless via NFC and Bluetooth works fine via an Anker Bluetooth speaker and my JBL Bluetooth headphones.
Sorry for digging an old thread, but I still have the same problem even after a bunch of software updates.
My issue with the AirPods is that they do not work after they connect. I take them out of the case, they connect (as expected), but as soon as I start playing something the music/video pauses and the sound switches to speaker (if I press play again it plays out loud). To make them work I need to go to bluetooth settings, disconnect them and connect them again. Then they will work almost flawlessy (minor intrerruption from time to time).
I have no issue with other BT speakers. I also use the AirPods with an iPad and laptop and no issues there.
My Nokia 8 software is up to date. AirPods firmware the same (checked on the iPad).
I tried re-pairing after each software update. I tried changin BT settings (absolute volume - dev settings; contact sharing and HD Audio: AAC) but no improvements.
Any ideas what else can I try?
Search for Oreo and Bluetooth problems. It seams to be a general issue for this Android Version. I have problems connecting my Phone with the car, too.
This is a long shot.
I have a pair of Bluetooth 4.1 Minirig speakers that can be set in stereo mode. However when in stereo mode one channel experiences dropouts. Running in mono mode is fine.
The issue is with the Nokia 7+'s Bluetooth transmission as when using other Bluetooth enabled devices to power the speakers the issue does not occur.
Anyone else had this issue when connecting stereo speakers or headphones and know of a solution?
I have checked: System > Developer Options > Bluetooth Audio Codecs and tried changing these setting but the changes did not "stick" and problem remained.
Maybe there is an alternative setting somewhere that can be tweaked.
Thanks in advance.
doowoppa65 said:
I have checked: System > Developer Options > Bluetooth Audio Codecs and tried changing these setting but the changes did not "stick" and problem remained.
.
Click to expand...
Click to collapse
I'm also having this issue: whenever I'm connecting my N7+ onto the car's audio system via Bluetooth I have to change the codecs to the correct one every single time to make it properly work (have sound/audio at all). The settings also don't stick or are not being saved. Also looking for a solution for this, unless an update miraculously fixes it.
Same problem here when connected to my car by bluetooth. Occasionally there is a dropout. This does not happen when my friends connect with their phones (oneplus 5, samsung, allview. or my old lg g4).
Changing the bluetooth audio codecs does not work as it does not remain selected and it switches to default. This, as i understood, happens on android 8 and has been resolved in the Pie beta and should be ok in the final Pie release.
When I raised the issue with the superbly talented nokia tech support they either act surprised as if its an unique issue to you or send you a list of compatible bluetooth protocols. Are we expected to change our cars and speakers to make the phone work?
I had this issue after installing garmin connect. Theres a thread over in the garmin forums (forums.garmin.com/forum/into-sports/garmin-connect-mobile-application/garmin-connect-mobile-android/1375800-audio-streaming-issues) about it. Also on the nokia forums (community.phones.nokia.com/support/discussions/topics/7000022239/). Seems to affect some phones on 8.1
Anyway, I'm on Pie beta now and the problem has gone away.