It would great to have a programmable button …
In a sense, you can already do that, as everything is under your control.
You could probably do something like “if the microphone kill switch is off, then use the volume buttons to do x and y instead of volume control”
I’d also be interested to see how hard it is to use the gyro-sensor to detect gestures like “double tap on the back” or so.
providing that you aren’t interested in using the volume control to control the output volume.
Sure. That’s why I linked it with the state of a killswitch, so you could switch how the volume control behaves. You could also link it with other states (home screen, screen is tapped) or activities (zoom in camera apps is common).
Admittedly, an additional button has more freedom.
That’s why gryo senser patterns are also interesting.
Or hey, the proximity sensor Double tap it to take a picture or something like that.
On Pinephone, SXMo operating system uses “volume up/down” and “power” buttons for navigating the menu (up/down and enter). It works amazingly well and is quite convenient.
“I would like to accept an incoming call via enabling microphone kill switch” - that was what I thought some month ago. Owning the phone seams to make a huge difference in how we mind about device functionality.
But “double tap on the back” sounds really nice. You tell your friends you phone PIN to unlock screen and let them try to unlock. Nothing happens. You take the phone, enter same numbers, double tap the back and your friends don’t even realize, that this double tap is an “enter” command.
I can imagine that gryo sensor patterns could be really nice for some better use cases. But how difficult is it to design different pattern to avoid using wrong commands or using commands when you didn’t want to do anything?
or rather the ‘double-tap’ would be customized to only respond to a SPECIFIC tap pattern that only YOU know
Like a music rhythm pattern? Just hope that you don’t miss one single tap while this 30s sequence.
We actually have that! It’s implemented in the lock screen. Sensitive to 10 different tap positions.
wow you guys thought about everything didn’t you ?
doesn’t seem to work on mine. Is that implemented in byzantium?
Irony is hard to get in the WWW, I guess @dcz just meant you can (un)lock your phone with a PIN - hence the 10 different tap positions: 0 - 9
I see. Just hoped I could wake up the device with a double tap (as in Sailfish OS). No need for unlocking
irony is hard to get even face to face not to mention when you’re wearing a face nappy
but anyway the screen doesn’t make it any less easy. i was ironic as well
At this rate, I may actually be able to get a PinePhone 2 before I get the L5 I ordered more than 2 years ago.
Yep ideally 2 sim slots and 1sd slot!
I hope I see it next year . probably not though haha
I feel lost that how many version of Librem 5 USA phone are there, which now we in the year of 2025?
There may be only one version of the Librem 5 USA, now officially called Liberty Phone, and it has 4GB RAM and 128GB disk.
That is “v2” in the sense that the Librem 5 USA used to come with less RAM and a smaller disk. It probably isn’t “v2” in the sense of customer’s wildest dreams.
I still stand by my original thinking about this hardware dev stuff… I think Purism took on way too much at once by trying to do an original hardware and software device.
I wish they had just focused on the software side and gotten us the best possible hardware (with kill switches and maybe a 3.5 jack still, but stop there). I bet the project would’ve been much more successful.
This probably isn’t a popular opinion among this crowd because I know some are concerned about the closed source ‘blobs’ that comes with certain hardware or whatever. And I would like that too, if it didn’t come at a high cost (it almost killed the entire experiment!!). I believe that requirement is what drove the infamous refund (or lack of) controversy ruining delivery dates (and Purism’s reputation).
You can only do so much at a time, and it appears to me the software ecosystem needs to be in much better shape before the Free hardware situation can be improved on.
Maybe I am being naive in some way not being expert at hardware engineering… but I know how hard software engineering is. And from years watching this project, through covid and all that crap that went down, it looks like hardware engineering is even harder. Taking on both at the same time was crazy and I’m still surprised they managed to technically pull it off.
It’s good they got to first base (barely), but not the home run we were hoping for.