I’m a robotics researcher. My interests include cybersecurity, repeatable & reproducible research, as well as open source robotics and rust programing.
A while back, I tried looking into what it would take to modify Android to disable Bluetooth microphones for wireless headsets, allowing for call audio to be streamed via regular AAC or aptX, and for the call microphone to be captured from the phones internal mic. This would prevent the bit rate for call audio in microphone being effectively halved when using the ancient HFP/HSP Bluetooth codecs, instead allowing for the same call quality as when using a wired headset. This would help when multitasking with different audio sources, such as listening to music while hanging out on discord, without the music being distorted from the lower bit rate of HFP/HSP. This would also benefit regular VoLTE, as the regular call audio quality already exceeds that of legacy Bluetooth headset profiles.
Although, I didn’t manage to tease apart the mechanics of the audio policy configuration files used by the source Android project, given the sparse documentation and vague commit history.
I’d certainly be fine with the awkwardness of holding up and speaking to my phone as if it was in speaker mode, but listening to the call over wireless headphones, in order to improve or double the audio quality. Always wondered what these audio policies fall back to when a Bluetooth device doesn’t have a headset profile, but it’s almost impossible to find high quality consumer grade Bluetooth headphones without a microphone nowadays.
For the call setting under Bluetooth audio devices, I really wish they would break out or separate the settings for using the audio device as a source or sink for call audio. Sort of like how you can disable HSP/HSF Bluetooth profiles for audio devices in Linux or Windows.
deleted by creator
Similarly reported (in more detail) by TechCrunch:
I’ll note that when using multiple windows, I recall that switching the user in one window would switch the user for all other windows as well, so support for simultaneous user sessions would probably have to be added as well.
This screenshot was from a Samsung Tab S8 Ultra. You can run 4 onscreen apps at a time (if you include a floating popup window in the mix) with multi windowing on Android 13 (outside Dex).
Getting the screenshot took a little tinkering, as after the first window split, getting the third instance of sync on the screen required using the Samsung side panel to drop an unrelated app in the third quadrant, then using the launcher to alt-tab the display to Fullscreen the third instance of sync, then alt-tabing back to Fullscreen the 3 app multi window view, then using the quick app switch gesture to swap out the unrelated app for the third instance of sync. It was a little overly complicated.
Multi tasking and window tiling in Samsung Dex is a lot easier, or more intuitive, to replicate the kind of thing, but I still prefer androids native launcher layout, as app windows don’t have needless title bars, and the same navigation gestures work better when not breaking out the mouse and keyboard.
Thanks so much for your hard work and the terrific beta release!
Here’s to the success of Lemmy, Sync for Lemmy, and the rest of the Fediverse,
Cheers! 🍻
Hello world!
~ from S4L!
I suspect this comment was posted to spell out the meme for those unfamiliar, but I wanted to thank you for transcribing it into text for those that also may be blind or visually impaired. With the loss of r/TranscribersOfReddit , I salute your contribution! Please keep at it!
https://www.theverge.com/2023/6/23/23771396/reddit-subreddit-community-transcribers-accessibility
I’m using a recent 42" LG OLED TV as a large affordable PC monitor in order to support 4K@120Hz+HDR@10bit, which is great for gaming or content creation that can appreciate the screen real estate. Anything in the proper PC Monitor market similarly sized or even slightly smaller costs way more per screen area and feature parity.
Unfortunately such TVs rarely include anything other than HDMI for digital video input, regardless of the growing trend connecting gaming PCs in the living room, like with fiber optic HDMI cables. I actually went with a GPU with more than one HDMI output so I could display to both TVs in the house simultaneously.
Also, having an API as well as a remote to control my monitor is kind of nice. Enough folks are using LG TVs as monitors for this midsize range that there even open source projects to entirely mimic conventional display behaviors:
I also kind of like using the TV as simple KVMs with less cables. For example with audio, I can independently control volume and mux output to either speakers or multiple Bluetooth devices from the TV, without having fiddle around with repairing Bluetooth peripherals to each PC or gaming console. That’s particularly nice when swapping from playing games on the PC to watching movies on a Chromecast with a friend over two pairs of headphones, while still keeping the house quite for the family. That kind of KVM functionality and connectivity is still kind of a premium feature for modest priced PC monitors. Of course others find their own use cases for hacking the TV remote APIs: