#AptX

0 Beiträge0 Beteiligte0 Beiträge heute

lj·rk @ #EH22Hm, now that the <a href="https://todon.eu/tags/Bluetooth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bluetooth</a> SIG pushes forward with <a href="https://todon.eu/tags/BLE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BLE</a> <a href="https://todon.eu/tags/Audio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Audio</a> using the open <a href="https://todon.eu/tags/LC3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LC3</a> codec (which is supposed to work for <a href="https://todon.eu/tags/HSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HSP</a>/#HFP mode as well, meaning finally proper Bluetooth microphone quality!), <a href="https://todon.eu/tags/Qualcomm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Qualcomm</a> finally opened up their <a href="https://todon.eu/tags/aptX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aptX</a> codec and donated it to the <a href="https://todon.eu/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> <a href="https://todon.eu/tags/AOSP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AOSP</a>, even part of the MTS test suite:<a href="https://android-review.googlesource.com/c/platform/test/mts/+/2298682" rel="nofollow noopener noreferrer" target="_blank">https://android-review.googlesource.com/c/platform/test/mts/+/2298682</a>

Terence EdenAwesome! Qualcomm open sourced the <a href="https://mastodon.social/tags/AptX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AptX</a> codec. <a href="https://www.reddit.com/r/Android/comments/11t16lk/qualcomm_has_open_sourced_its_aptx_and_aptx_hd/" rel="nofollow noopener noreferrer" target="_blank">https://www.reddit.com/r/Android/comments/11t16lk/qualcomm_has_open_sourced_its_aptx_and_aptx_hd/</a> ...and now <a href="https://mastodon.social/tags/Lineage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Lineage</a> supports it! My old Android phone final sounds brilliant on my Bluetooth headphones.

lj·rk @ #EH22Since I just shared some advice on in ear monitors I can also share it here:If your <a href="https://todon.eu/tags/inear" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#inear</a> <a href="https://todon.eu/tags/headphones" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#headphones</a>/#earphones or <a href="https://todon.eu/tags/IEM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IEM</a> 's hurt, and you're using ones with a nozzle+replaceable tip construction, chances are the nozzle has a too large diameter. Many (most?) nozzles are 5mm in diameter or nozzle size "T400". There are other sizes out there, notable T100 (3mm). Some manufacturers produce mostly T100 (or T200) nozzles, such as Shure (although a bit pricy). An easy way to find T100 models is to go to the website of comply who manufacture foam tips in various sizes, select T100 and look for the supported models in the compatibility tab: <a href="https://www.complyfoam.com/products/comply-100-series" rel="nofollow noopener noreferrer" target="_blank">https://www.complyfoam.com/products/comply-100-series</a>Additionally, I can recommend buying earphones with detachable cables. The plug is standardized (e.g. MMCX) which means you can a) replace broken cables and b) use the ear unit from say Shure with the <a href="https://todon.eu/tags/Bluetooth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bluetooth</a> module from LinSoul and switch between wireless and wired. You can also upgrade from Bluetooth 4 to <a href="https://todon.eu/tags/BLE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BLE</a> <a href="https://todon.eu/tags/Audio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Audio</a> when it will be more available or to BT modules that support <a href="https://todon.eu/tags/AptX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AptX</a>, <a href="https://todon.eu/tags/LDAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LDAC</a>, <a href="https://todon.eu/tags/AAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AAC</a> or other special audio codecs whenever you feel like it. This prolongs the life time of your product. <a href="https://todon.eu/tags/hifi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hifi</a> <a href="https://todon.eu/tags/RightToRepair" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RightToRepair</a>

Maxi 10x 💉Prüft mal, ob ihr libfreeaptx installieren könnt (Arch hat’s). <a href="https://chaos.social/tags/PulseAudio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PulseAudio</a> kann damit endlich den Codec für ausgehende und eingehende Audioverbindungen wie verbundene Smartphones nutzen!Eigentlich hätte das schon vor einem Jahr funktionieren sollen, aber jetzt tut’s hier jedenfalls endlich. Prüfen, welcher Codec genutzt wird, könnt ihr in PavuControl. <a href="https://chaos.social/tags/aptX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aptX</a>

Kim Sudenlehto<a href="https://floss.social/@9to5linux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@9to5linux@floss.social</a> Do <a href="https://mk.nixnet.social/tags/Bluetooth" rel="nofollow noopener noreferrer" target="_blank">#Bluetooth</a> headsets have full support yet? My <a href="https://mk.nixnet.social/tags/LinuxMint" rel="nofollow noopener noreferrer" target="_blank">#LinuxMint</a> <a href="https://mk.nixnet.social/tags/pipewire" rel="nofollow noopener noreferrer" target="_blank">#pipewire</a> solution was to ditch <a href="https://mk.nixnet.social/tags/aptX" rel="nofollow noopener noreferrer" target="_blank">#aptX</a> (which doesn't work properly) in favor of AAC to get HQ audio, but HQ audio + working microphone seems to be still a problem. Mostly it just means I have to route <a href="https://mk.nixnet.social/tags/Discord" rel="nofollow noopener noreferrer" target="_blank">#Discord</a> voice chat through my phone, but it's a pain. Since <a href="https://mk.nixnet.social/tags/Android" rel="nofollow noopener noreferrer" target="_blank">#Android</a> is almost a <a href="https://mk.nixnet.social/tags/linux" rel="nofollow noopener noreferrer" target="_blank">#linux</a>, and my headset works properly there, shouldn't getting Bluetooth headsets working be a relatively simple matter?

heise online (inoffiziell)Noch ist Zeit bis Weihnachten – TechStage zeigt, welche Kopfhörer sich als Geschenk eignen und was man beim Kauf beachten muss, um Lieferengpässe zu vermeiden. Noch ist Zeit bis Weihnachten – wer Lieferengpässe und überforderte Paketzusteller vermeiden will, sollte sich trotzdem zeitnah nach Weihnachtsgeschenken umsehen. <a href="https://www.techstage.de/ratgeber/geschenke-ratgeber-kopfhorer-true-wireless-over-ear-anc-aptx-and-co-ab-30-euro/9pld17v" rel="nofollow noopener noreferrer" target="_blank">Geschenke-Ratgeber Kopfhörer: True Wireless, Over-Ear, ANC, AptX & Co. ab 30 Euro</a>

LucifarGundam<a href="https://social.kaitaia.life/users/nick" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@nick</a> <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> <a href="https://fosstodon.org/@briar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@briar</a> My bad- I haven't had my coffee yet and misunderstood.As I still wake up, speaking from a pinephone user perspective::: - A fully <a href="https://qoto.org/tags/encrypted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encrypted</a> <a href="https://qoto.org/tags/filesystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filesystem</a>, with optional support for hardware key (like <a href="https://qoto.org/tags/solokey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#solokey</a>, or <a href="https://qoto.org/tags/nitrokey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nitrokey</a>) <a href="https://qoto.org/tags/decryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#decryption</a> ++Not sure about hw key, but encrypted fs is relatively easy on most Linux distros - NO <a href="https://qoto.org/tags/Fingerprint" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fingerprint</a> Scanner or <a href="https://qoto.org/tags/Biometrics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Biometrics</a> at all ++<a href="https://qoto.org/tags/pinephone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pinephone</a> doesn't have that at all - <a href="https://qoto.org/tags/NFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NFC</a> that can only be toggled on temporarily, and automatically shuts off after X amount of time ++Probably a feature to be released in the near future - <a href="https://qoto.org/tags/Bluetooth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Bluetooth</a> 5+ with <a href="https://qoto.org/tags/A2DP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#A2DP</a>; <a href="https://qoto.org/tags/AptX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AptX</a> and <a href="https://qoto.org/tags/BLE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BLE</a> with a more security focused method of <a href="https://qoto.org/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#authentication</a> ++From the wiki "Bluetooth: 4.0, A2DP"; could probably swap it out though. - All internet connections routed through @torproject (or something similar), with a <a href="https://qoto.org/tags/killswitch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#killswitch</a> if the connection is dropped ++Maybe configure a distro to do so? I know there's various killswitches on the back. - Privacy focused <a href="https://qoto.org/tags/browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#browser</a> with something like <a href="https://qoto.org/tags/SSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSL</a> Everywhere; <a href="https://qoto.org/tags/WebRTC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebRTC</a> and JS disabled by default, with easy toggle for "trusted" websites, which would allow JS and Video etc ++Never tried this specific setup myself-ill have to give it a go. - <a href="https://qoto.org/tags/Decentralized" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Decentralized</a> messaging; voice chat; video conferencing; forums and blogs, like where <a href="https://qoto.org/tags/Briar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Briar</a> is being taken by @briar (though the voice; video and other creature comforts are as yet unavailable) ++I used <a href="https://qoto.org/tags/fractal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fractal</a> as well as ssh into my personal communication server - No closed source Modem/Wifi/Bluetooth binary blobs ++Iirc, pinephones modem is open. - Securely Containerized SMS/MMS ++Sms/mms is still unstable but working - Password Manager with support for <a href="https://qoto.org/tags/OTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OTP</a>; <a href="https://qoto.org/tags/TOTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TOTP</a> and <a href="https://qoto.org/tags/Fido2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fido2</a> ++I keep being referred to bitwarden. Not sure if this applies. - <a href="https://qoto.org/tags/GPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GPS</a> <a href="https://qoto.org/tags/Spoofing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Spoofing</a> by default ++Not aware of any mobile distro doing this be default =======≠===≠=≠================≠===≠===≠== I would like to see more Linux phone options/development out there in the wild...

AnotherKiwiGuyI was thinking about my post about a week ago, re. the <a class="hashtag" href="https://social.kaitaia.life/tag/freedomphone" rel="nofollow noopener noreferrer" target="_blank">#FreedomPhone</a> (see the link below). It got me wondering - What would I actually want in a <a class="hashtag" href="https://social.kaitaia.life/tag/freedom" rel="nofollow noopener noreferrer" target="_blank">#Freedom</a> and <a class="hashtag" href="https://social.kaitaia.life/tag/privacy" rel="nofollow noopener noreferrer" target="_blank">#Privacy</a> respecting <a class="hashtag" href="https://social.kaitaia.life/tag/phone" rel="nofollow noopener noreferrer" target="_blank">#phone</a>? Maybe things like: - A fully <a class="hashtag" href="https://social.kaitaia.life/tag/encrypted" rel="nofollow noopener noreferrer" target="_blank">#encrypted</a> <a class="hashtag" href="https://social.kaitaia.life/tag/filesystem" rel="nofollow noopener noreferrer" target="_blank">#filesystem</a>, with optional support for hardware key (like <a class="hashtag" href="https://social.kaitaia.life/tag/solokey" rel="nofollow noopener noreferrer" target="_blank">#solokey</a>, or <a class="hashtag" href="https://social.kaitaia.life/tag/nitrokey" rel="nofollow noopener noreferrer" target="_blank">#nitrokey</a>) <a class="hashtag" href="https://social.kaitaia.life/tag/decryption" rel="nofollow noopener noreferrer" target="_blank">#decryption</a> - NO <a class="hashtag" href="https://social.kaitaia.life/tag/fingerprint" rel="nofollow noopener noreferrer" target="_blank">#Fingerprint</a> Scanner or <a class="hashtag" href="https://social.kaitaia.life/tag/biometrics" rel="nofollow noopener noreferrer" target="_blank">#Biometrics</a> at all - <a class="hashtag" href="https://social.kaitaia.life/tag/nfc" rel="nofollow noopener noreferrer" target="_blank">#NFC</a> that can only be toggled on temporarily, and automatically shuts off after X amount of time - <a class="hashtag" href="https://social.kaitaia.life/tag/bluetooth" rel="nofollow noopener noreferrer" target="_blank">#Bluetooth</a> 5+ with <a class="hashtag" href="https://social.kaitaia.life/tag/a2dp" rel="nofollow noopener noreferrer" target="_blank">#A2DP</a>; <a class="hashtag" href="https://social.kaitaia.life/tag/aptx" rel="nofollow noopener noreferrer" target="_blank">#AptX</a> and <a class="hashtag" href="https://social.kaitaia.life/tag/ble" rel="nofollow noopener noreferrer" target="_blank">#BLE</a> with a more security focused method of <a class="hashtag" href="https://social.kaitaia.life/tag/authentication" rel="nofollow noopener noreferrer" target="_blank">#authentication</a> - All internet connections routed through <a class="u-url mention" href="https://mastodon.social/@torproject" rel="nofollow noopener noreferrer" target="_blank">@torproject</a> (or something similar), with a <a class="hashtag" href="https://social.kaitaia.life/tag/killswitch" rel="nofollow noopener noreferrer" target="_blank">#killswitch</a> if the connection is dropped - Privacy focused <a class="hashtag" href="https://social.kaitaia.life/tag/browser" rel="nofollow noopener noreferrer" target="_blank">#browser</a> with something like <a class="hashtag" href="https://social.kaitaia.life/tag/ssl" rel="nofollow noopener noreferrer" target="_blank">#SSL</a> Everywhere; <a class="hashtag" href="https://social.kaitaia.life/tag/webrtc" rel="nofollow noopener noreferrer" target="_blank">#WebRTC</a> and JS disabled by default, with easy toggle for "trusted" websites, which would allow JS and Video etc - <a class="hashtag" href="https://social.kaitaia.life/tag/decentralized" rel="nofollow noopener noreferrer" target="_blank">#Decentralized</a> messaging; voice chat; video conferencing; forums and blogs, like where <a class="hashtag" href="https://social.kaitaia.life/tag/briar" rel="nofollow noopener noreferrer" target="_blank">#Briar</a> is being taken by <a class="u-url mention" href="https://fosstodon.org/@briar" rel="nofollow noopener noreferrer" target="_blank">@briar</a> (though the voice; video and other creature comforts are as yet unavailable) - No closed source Modem/Wifi/Bluetooth binary blobs - Securely Containerized SMS/MMS - Password Manager with support for <a class="hashtag" href="https://social.kaitaia.life/tag/otp" rel="nofollow noopener noreferrer" target="_blank">#OTP</a>; <a class="hashtag" href="https://social.kaitaia.life/tag/totp" rel="nofollow noopener noreferrer" target="_blank">#TOTP</a> and <a class="hashtag" href="https://social.kaitaia.life/tag/fido2" rel="nofollow noopener noreferrer" target="_blank">#Fido2</a> - <a class="hashtag" href="https://social.kaitaia.life/tag/gps" rel="nofollow noopener noreferrer" target="_blank">#GPS</a> <a class="hashtag" href="https://social.kaitaia.life/tag/spoofing" rel="nofollow noopener noreferrer" target="_blank">#Spoofing</a> by default That's all I can think of for now, what would YOU like to see in a Privacy focused Phone? <a href="https://social.kaitaia.life/notice/A9OiFyZ1Sd0YXjd200" rel="nofollow noopener noreferrer" target="_blank">https://social.kaitaia.life/notice/A9OiFyZ1Sd0YXjd200</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik: