zlacker

[parent] [thread] 7 comments
1. stacke+(OP)[view] [source] 2025-12-05 16:16:16
If it catches traction, there will be usb-connected phone cases that expose these switches to physical controls.
replies(2): >>jeffbe+J8 >>Nifty3+wf
2. jeffbe+J8[view] [source] 2025-12-05 16:54:01
>>stacke+(OP)
I don't think that's what anyone means by "physical controls" and if they do, then they don't know what they are talking about.
replies(1): >>stacke+Zv
3. Nifty3+wf[view] [source] 2025-12-05 17:21:38
>>stacke+(OP)
I do not really understand what you mean by this. Can you elaborate or clarify what you mean?
replies(1): >>stacke+dv
◧◩
4. stacke+dv[view] [source] [discussion] 2025-12-05 18:31:56
>>Nifty3+wf
I mean since it's linux phone with (hopefully) open architecture, it should be possible to create an external usb device that exposes any functionality.

Like, to keep core functionality simple and open it for extensions ("extra battery", "knobs and switches", "ethernet" etc)

replies(1): >>fsflov+ve1
◧◩
5. stacke+Zv[view] [source] [discussion] 2025-12-05 18:35:06
>>jeffbe+J8
"Physical controls" are those that you can physically sense. My point was everyone needs different things, so it's possible to keep core functionality simple and let users add what they need, via extensions. Like dongle hell but better.
◧◩◪
6. fsflov+ve1[view] [source] [discussion] 2025-12-05 22:13:48
>>stacke+dv
But if it does not really cut the power to hardware components, how will you trust that it turns your mic off?
replies(2): >>Nifty3+ZH1 >>stacke+UV2
◧◩◪◨
7. Nifty3+ZH1[view] [source] [discussion] 2025-12-06 02:12:24
>>fsflov+ve1
Yes, this is what I'm getting at. I want to KNOW that the function is off, and that nothing can turn it back on except a physical action by me.
◧◩◪◨
8. stacke+UV2[view] [source] [discussion] 2025-12-06 16:38:29
>>fsflov+ve1
There are many other use cases, physical control are not used only for cutting power of components.
[go to top]