$ bluetoothctlAre you even a true power user if you don’t tattoo your headphones MAC address on your forearm?
What if your heaphones break?
If a power user, perhaps. But for a good UX enjoyers:
$ bluetoothctl devicesLetters? On my screen? Instead of icons and pictograms that I can click with my mouse? Preposterous!
You can move your mouse over them. 😆
I just tab and pray
Paired devices are stored and have proper names
This. Bind connect command to a keyboard shortcut. Live in peace.
Statements dreamed up by the utterly deranged
On Mac, I had one touchbar button that connected/disconnected the headphones and another that handed them over to the phone or from the phone to the laptop. Plus commands in Alfred that did the same. And same on the phone in the dropdown menu.
Ngl I really want to know what the tick icon actually does now.
If you hover on it (without clicking, resist the temptation) it says it is for “Mark/unmark this device as trusted”.
Which in turn doesn’t quite explain what happens. For me, the relevant difference was that ‘trusted’ devices autoconnect.
Well there’s “trusting” a device, “pairing” with a device and “connecting” to a device. Which need to be done in that order
Which makes it even more confusing what the button does
This bastard of an app manages to expose too much of the underlying processes and logic, of which I don’t care, in the utterly uninformative format. The OP forgot to mention that upon first pairing my headphones, I have to fend off three different notifications about ‘auth requests’, that provide me with no explanation what happens if I do or don’t satisfy said requests. These also reappear after the headphones disconnect for some inexplicable reason, until I give up on learning further details and click ‘always auth’. Which seems to help with the disconnections. Apparently some audio profiles are also occasionally unavailable unless I appease the blue fucker with ‘always auth’.
Sometimes the headphones fail to connect, and all I get is some cryptic error message, with the only understandable word being ‘timeout’.
The tray menu has a shitload of items which I never need, and then always lists devices to which I can reconnect, even when they’re already connected and have separate (and dynamic) menu items to disconnect from them. Plus each device is listed like they have titles of nobility, something like ‘audio and input profiles on HeadphonesModel’.
Lmfao sounds like Bluetooth alright
The matter of wonder is that I never needed this ‘auth’ thing or the ‘trust’ thing in Windows, Mac, or Android, and never had recurring disconnection problems, before this experience. I just paired a device and then clicked ‘connect’ or ‘disconnect’ and went about my business. In fact, I was baffled by how people seem to always have some issues, devices connecting randomly, etc.
Even Bluetooth range seems to have dropped compared to other platforms. My phone can reach the headphones over a large apartment, while laptop loses them if I walk behind a wall.
Bizarre, what kernel and distro?
You can pair and connect without trusting. It will ask for authorization.
Alright, do not trust device. Guess what that mf autoconnects anyways!
Love the format, such shade
I personally like its adamant REFUSAL to be bullied into showing the actual state of devices. DMESG knows, because notifications show the correct state, but Blueman is over here IE6ing.
Wow I see this post exactly one day after spending 4 hours tearing my hair out trying to connect a switch pro controller using blueman only to find out that I apparently have to use bluetoothctl because blueman can’t for some reason.
Anyone run into this problem?
I feel like there’s something you need to use bluetoothctl for on every system
For me it was trying to pair with a meshcore companion using a passcode
a meshcore heathen? in this economy? serves you right for not using meshtastic
/s
Meshtastic is completely dead here, apart from a few derelict repeaters. Meshcore is alive and linking 4 states on the east of Australia
I’ve only worked once with a UX person and all they did was order other people to produce design documents before any software was written. Like, he didn’t design anything himself and didn’t even critique others’ designs. He made over $300K and eventually left for a job on the west coast making twice as much. He stopped talking to me entirely after the client had me write a prototype TV guide-type app for Blackberry. I created it entirely myself and the client loved it and wanted it released to the public exactly as it was. UX guy insisted (client didn’t care at all) that all software needed a design document before any coding could take place, so he was forced to order somebody else to produce a design document for my app which already existed. He wouldn’t even look at me when we passed in the hall after this.
I assume that this is not actually what a UX person is supposed to be doing, but I have no idea what their real job is.
I’m guessing that the design documents might’ve been something in the vein of ‘user stories’ (if I correctly recall their name), which describe what some typical users would want to do with the app, so that the actual UI design would focus on these features being available front and center. This is a very legitimate design technique, and a good designer should always question why any elements must be present in the UI and whether they solve the user’s goals.
This Blueman thing would definitely benefit from such approach, because right now it exposes a lot of technical details about which I don’t care, while simultaneously making my everyday operations with it inconvenient.
By the way, @ChickenLadyLovesLife@lemmy.world, I brought up user stories in particular because they should be initially written or at least verbalized by either the target users or clients like managers. Neither designers nor programmers can know exactly what the target user’s needs are, or they may think they know but be mistaken — because they don’t have what’s called the domain knowledge, i.e. expertise of the target users.
Of course, another major tool in a designer’s workflow is testing with target users before release, including with rough mockups — so any misunderstanding of users’ goals and workflow can be caught in time.
For the context, I’m a dev who mostly does backend. But understanding design is interesting and helpful.
another major tool in a designer’s workflow is testing with target users before release
Lol you should have seen this UX dude’s face when I suggested doing exactly this. It’s hard to imagine an actual live human being saying “users don’t know what they want” but that is exactly what he said. It should be no surprise that this company routinely produced one-star apps, and also no surprise that the company was a routine winner of the Worst Company of the Year contest.
Yeah that dude was just a dick, but probably confidently, and in a field people don’t know much about, so he was able to get away with it.
I work with UX people frequently, and while they do love a good style guide, they’re usually more concerned with the overall usability, legibility, and accessibility of an application. They’re the people who (should) ensure your application works as expected and follows design and accessibility standards.
follows design and accessibility standards
Ah, this reminded me of another reason this dude hated me. One of my responsibilities with this gig was ensuring that the client’s mobile apps passed accessibility testing. Making an app accessible is tedious work and every time we released an update the accessibility would be broken again. I tried to get this dude to bake the accessibility requirements into the design documents themselves on the off chance that the other developers would actually read the documents (lol as if) and make accessibility work from the get-go. He wasn’t having it and couldn’t be convinced that it mattered if blind people could use the apps or not. I had to sic the client (who faced enormous fines for failed accessibility tests) on him to get him to do it.
Heh.
Design documents are only useful if those deciding the design are making it and are ready before the coding starts.
And then there is this confusion of which “Design Document” one is talking about. It could be a UI/UX document or it could be the software design document, which would comprise multiple flow-diagrams, helping anyone pick up a project for maintenance and extension.if those deciding the design are making it
This kinda depends. User stories document the typical goals and workflow of the users with the app, and thus should come from the target users or at least the client like a manager. The designer is not qualified to make the user stories since they don’t know the business domain, as it’s called. But they know how to organize the UI for any particular goals.
Yes, but it is also important to understand that not having a Design Document does not equate to not having a Design.
There was 1 project where the users of the UI I was making were not nearby (in most cases my direct senior was also the user) and most of the UI/UX expectation were passed on verbally. I then made a basic model and then iterated over it with repeated feedback from the target users.So the point is that anyone putting a design document on a pedestal (like an interviewer at one of my past applications) is most probably spewing garbage.
Trust the devs
I love this window.
In my Head I’m Reading all of this in Tantacrul’s voice
That’s why I, as a seasoned programmer, keep my fingers out of UI design. I leave that to the professionals.
Is there a simple GUI for
bluetoothctl?xterm
yes
most intuitive qt software
💯
hopefully a FOSS organization will hire the person who made this
please never vote or reproduce, OP.
I’m gonna vote and reproduce with your mum even harder now
I also vote for their mom
