OK my VOIP/SIP works on WM6 and my Internal earphone works with SIP on my TyTN WM6. Thanks to the great work off that thread's contributers. I can use both the internal speaker phone and the internal earphone of my TyTN. The sound quality ,however, is another topic: mine is very choppy. I can not even judge the other quality factors.
I read a lot of SIP/VOIP postings but did not find much on improving the audio quality under WM6. Third party SIP clients most times have codec, jitter, buffer and other voice and audio adjustment possibilities. The only very technical reference I found is Windows CE Networking Team WebLog.
I can compare the audio quality of my HTC TyTN WM6 SIP with a Linksys WIP 330 WiFi phone (WM 4.2, SIP) through the same WiFi Router. ADSL at above 10 mbs and 1 mbs upload. The WIP330 sounds is a bit sharp (high hiss), but almost no chopped off sound.
Perhaps the lack of those features is why HTC left SIP support out under WM6?How is your audio quality on your device under WM6?
Same here. Using voip on Kaiser with Dutty's Touchflo ROM. Got it set up with voip.com and the call quality is lousy (choppy, jitter, etc.). It's about the same whether I use wifi or 3g. Any recommended solution for this? I know my broadband wifi connection is good since I use the softphone from my laptop over wifi with execellent results. Would trying a different codec help? If so which one and how would I set that up? Thanks.
To my knowledge, this is the first aviation headset that allows a BT connection to a phone you can talk on the phone hands free while flying. I can get it to connect and make/receive phone calls without a problem, but there is a semi-obnoxious hum/high pitch/static noise and I can't seem to make it go away, and also a ticking sound that increases and decreases volume at random. I've read about other pilots having great success with the BT portion, but I'm wondering if maybe the Tilt is only "compatible" with certain BT devices. Anyone have any thoughts/knowledge on the selective compatibility issue, or have heard of similar issues with BT in general? This is an incredible headset worth the money with it's MP3 input, noise cancelling, and everything. I'd hate to have to consider taking it back because I can't use the currently exclusive BT feature.
BT is comprised of a series of standards defining each individual interface type. I would wager that the problem is with the headphones more so than with the way BT is implemented in the phone.
That said, you can confirm the performance by swapping headsets or phones to see if the problems shifts.
[Q] Does LG G2 support Audio tunneling on kitkat? Just like Nexus 5?
Audio Tunneling to DSP
For high-performance, lower-power audio playback, Android 4.4 adds platform support for audio tunneling to a digital signal processor (DSP) in the device chipset. With tunneling, audio decoding and output effects are off-loaded to the DSP, waking the application processor less often and using less battery.
Audio tunneling can dramatically improve battery life for use-cases such as listening to music over a headset with the screen off. For example, with audio tunneling, Nexus 5 offers a total off-network audio playback time of up to 60 hours, an increase of over 50% over non-tunneled audio.
Media applications can take advantage of audio tunneling on supported devices without needing to modify code. The system applies tunneling to optimize audio playback whenever it's available on the device.
Visualizer showing loudness enhancer audio effect
Visualization of how the LoudnessEnhancer effect can make speech content more audible.
Audio tunneling requires support in the device hardware. Currently audio tunneling is available on Nexus 5 and we're working with our chipset partners to make it available on more devices as soon as possible.
Click to expand...
Click to collapse
https://developer.android.com/about/versions/kitkat.html
I'd also like to know that.
Hello guys,
I'm facing a problem and I simply can't seem to find any info on the web on how to go about fixing it...
There is a sound quality issue when I connect my Huawei P8 Lite to my Alpine UTE-72BT Head Unit. Aside from the fact that it keeps disconnecting at random, it sounds as though the bitrate isn't high enough on transfer, thus producing sort of a "crackling" effect on the highs (something similar to clipping). I've also read that some other users have experienced issues with bass being much louder, although I can't say for sure that this is the same case.
It's regardless of the music source, be it internal storage, with 320 kbps mp3s (converted from FLACs) or Spotify on extreme quality (both from downloaded and from streaming on LTE). I haven't faced the same issue with a Microsoft Lumia 640, for example, and neither with music played from USB, so the issue is isolated to the P8. The issue seems to "fade away", so to speak, if connected to the phone via AUX cable (Cordial cable, high quality, as well). The fact of the matter is that: 1. Music played over AUX tends to be more dull, as if though it applies a wide band pass filter and 2. AUX lacks the ability to control phone media via the headunit, which makes the point of having a bluetooth player absolutely pointless.
So far, I've tried the following:
- deactivate wireless - as I've heard speculations of bluetooth and wireless being combined into a single chip;
- use EQing apps, such as Dolby Atmos (actually, this was the moment I noticed the crackling, on account of the fact that highs can be controlled much better with Dolby's app);
- Update firmware on HU (more like a refress, to be honest. I was already running the latest bluetooth firmware);
- Updated to Marshmallow (B550);
I'm guessing that there is some issue with the codecs used to transmit data to the player, although I wouldn't know how to go about modyfing them, as the only resource I've found, up to now, is related to a Samsung S2. Counting on the fact that there might be some OS modifications (in what regards coding standards and such), I consider that the resource would not be very helpful.
If there's anyone out there willing to help me find a solution, I would very much appreciated, and, also, if there is any info that I have omitted, please don't hesitate to ask. Thank you!
The OnePlus 5 has those 3 options but I do not know the difference between them or which is best to use. Any help would be appreciated. Thank you!
+1
Both the phone and Bluetooth device have to support AptX for it to work, so often your issue resolved by that.
AptX will provide better sound than SBC. SBC is the default codec used by the A2DP Bluetooth profile.
So, in short, if your headphones/speakers have AptX, use that. If they don't, SBC.
What happens if you choose aptX if your device doesn't support it?
yubimusubi said:
What happens if you choose aptX if your device doesn't support it?
Click to expand...
Click to collapse
It will probably just switch to SBC so the connection will work, as that's the baseline standard in Bluetooth. I couldn't say with absolute certainty, as my OP5 hasn't arrived yet.
AptX is a proprietary thing - someone other than the Bluetooth consortium developed it and licenses it. That's why not everything has it - you have to pay to use it in the products you make. They created AptX because the default Bluetooth audio profile pretty much sucks when you start to examine how it butchers bit depth and sample rates just to cram audio data across a low power wireless signal.
On the flip side of that coin - yeah, AptX is better (and I'd use it if both devices supported it) but the audio quality differences are probably not going to readily apparent when listening to $20 to $50 Bluetooth devices. It's been my experience that it takes a somewhat trained ear and better-than-good equipment to be able to easily spot the difference. So, if you're an audiophile, you probably already know to stay away from Bluetooth for the best quality sound. If you're not an audiophile, try to use the best Bluetooth profile you can, but don't sweat it too much.
The A2DP profile is negociated at pairing and the best supported by both devices is picked (SBC < AptX < AptX HD). Problem is that the codec is just one link in the whole daisy chain. Other equally important aspects:
- music source quality (don't expect 128 kbps CBR mp3 to sound good)
- DAC and amplifier (each and every sound system that converts bits to sound has these!)
- speakers (from those in IEM's to those in BT boom boxes - they are all speakers)
So just that you're using AptX doesn't imply you are listening to high quality sound and probably implementing AptX and putting its logo on the product is the cheapest and least development intensive way to raise the price of a product.
Just my two (euro) cents...
Hi,
The question here is how the phone behaves when a higher quality codec has been selected (eg aptX) and a standard bluetooth headset (SBC - only )has been connected?
So far it seems to work (but then the question is why there is a selection available)
Best Regards
Joerg
My wild guess is that tis setting acts like a low-pass filter threshold. The phone will negotiate the highest available option without going above setting.
If the setting is AptX, the phone and speaker support AptX HD, the connection will be made at AptX quality. If the speaker only supports SBC, the connection will be made with SBC.
Honestly I don't see the point in such a setting. 99% of the people would want the best quality available anyway.
Is there a power consumption difference?
Sent from my ONEPLUS A5000 using Tapatalk
daniel_loft said:
My wild guess is that tis setting acts like a low-pass filter threshold. The phone will negotiate the highest available option without going above setting.
If the setting is AptX, the phone and speaker support AptX HD, the connection will be made at AptX quality. If the speaker only supports SBC, the connection will be made with SBC.
Honestly I don't see the point in such a setting. 99% of the people would want the best quality available anyway.
Click to expand...
Click to collapse
It makes sense to have the setting *if* for some reason you want to force SBC or the non-HD aptX. I have it set to aptX HD right now and it seems to work with my car (I'm about 95% sure it doesn't support aptX).
The real question is, if it fails back appropriately, why on Earth would OnePlus set the *default* to SBC?
@aa_chow: There surely is a consumption difference. SBC was designed decades ago with low computational complexity in mind (among others). On the current smartphone hardware (which is probably on par with a medium desktop from 5-6 years ago) the difference would be so small that measurements are impossible (you might see a difference on the battery life of the speakers, but I wouldn't loose my time there) .
@yubimusubi: I cannot even find the reason why that setting is even there! It only limits the best usable codec, which makes no sense to me. Maybe you can find more answers on the oneplus forums.
lag
with the sb, i experience music lag from when i have played in 1 minute and it continues, is it low power consumption or something on sbc? I'm gonna try the apex option when i get home to check if its better.
I'm suffering micro breaks on HD audio (320 bitrate MP3) from aptX HD, aptX or SBC.
Is there a way to correct it?
All my files are stored at 320 and I doesn't have time to convert to a bitrate of 128
Edit: No issues with iPhone 7+ and Huawei P10 using the same BT headset and MP3 files
bartito said:
I'm suffering micro breaks on HD audio (320 bitrate MP3) from aptX HD, aptX or SBC.
Is there a way to correct it?
All my files are stored at 320 and I doesn't have time to convert to a bitrate of 128
Edit: No issues with iPhone 7+ and Huawei P10 using the same BT headset and MP3 files
Click to expand...
Click to collapse
I have an issue on my International LG G6 where it sounds like the 24 bit lossless tracks are essentially dropping frames to borrow a gaming term. Then it will correct itself. It happened on my VW and the problem persists in my wife's new Subaru.
The LG G6 sports Aptx HD. Any ideas?
i prefer aptX but then again ive been using it quite a while now
APTX-HD do not work on One Plus 5. The music hacks constant.