Earlier quoted context omitted.
It probably doesn't help, but it definitely isn't the reason. Most people still do their work on desktops with full-sized keyboards and they already don't use those keys there.
So how they e.g. move around cells in the spreadsheet or documents?
Open-Sourcing our Firmware
201–210 of 382 posts
Re: Open-Sourcing our Firmware
#202Earlier quoted context omitted.
The problem starts with the fact that the device doesn't have any way of showing that it was modified, and some of the frequencies involved are license-restricted (especially in 5GHz wifi bands - 2.4GHz is dumping ground free-for-all because of aircraft ovens anyway). So, let's say you modify something with your own firmware, break rules about ISM spectrum - or worse, mess with SDR hard enough you break some licensed…
The FCC is very familiar with inconspicuously modified commercial devices - hams have been doing it since before "firmware" was even a word. The fact that it's replacing some code on a chip instead of a shunt resistor on a PCB really doesn't make a difference. And if this really was really the main issue, it seems pretty easy to just sign the firmware - I'm pretty sure many vendors do it already.
The code being secret is more of "trade secrets" than anything legal.
Re: Open-Sourcing our Firmware
#203Earlier quoted context omitted.
Especially on a 13" screen. I have an XPS 13 with a 4k screen and I never use it at native resolution undocked because I'd need a magnifying glass to read anything on it.
You're always using it at native resolution, you're just adjusting your renderer settings. Nobody's saying your fonts should be tiny. I'm saying they should be rendered in high resolution. I have the same computer and display. I run it at 4k native but nothing is small, no magnifying glass required.
No, when I wrote 'native resolution' I meant 1:1 pixel mapping, which is pretty obvious by context. Nobody has a laptop with a CRT on it these days.
Re: Open-Sourcing our Firmware
#204Earlier quoted context omitted.
I've been using a Framework laptop for a month on Ubuntu 21.10 and pretty happy with it. Some hiccups but mostly answered by digging through forums. Battery life in operation is excellent, but it does drain 30% in 8 hours when on suspend which is a bit much. Not a dealbreaker but hope this can be solved.
High battery drain during standby on Linux can be due to the system not entering the proper sleep state. I had this happen to me on an AMD machine lately, in that case disabling secure boot solved the issue. Here is a pretty detailed blog post in checking if that is the problem and how to deal with it on intel systems https://01.org/blogs/qwang59/2018/how-achieve-s0ix-states-li...
Lovely...
Re: Open-Sourcing our Firmware
#205Earlier quoted context omitted.
Because I'm down the rabbit hole of highly customized keyboards, at one point I did a frequency analysis of the keys I use the most. Guess what was the most frequently used key? Cursor down followed by cursor up. For example, cursor down was pressed ~2.5x more times than space, or ~4 times more than letter E, which is was the most frequently used letter. Guess what are the smallest keys on a Mac-type keyboard (the la…
Do you scroll with the arrows keys?
Either that, or PgUp/PgDown
Re: Open-Sourcing our Firmware
#206Earlier quoted context omitted.
Are you talking about personal testimonials, or published data? If it's published data, mind sharing a link?
It was a recent thread here on HN. Let me see if I can find it... This comment: https://news.ycombinator.com/item?id=29807585 Some of these issues could be subjective, and I shouldn't decide based on that single report alone, but it was enough reason to reconsider the purchase, especially since, like I said, I really don't need a new machine.
Re: Open-Sourcing our Firmware
#207I checked the keyboard debouncing logic [0] and it was fine. Some keyboards from other manufacturers, notably Lenovo Thinkpads, have absurd debouncing algorithms that scramble keys or add delays, so it's good to see Framework has a correct solution. [0]: https://github.com/FrameworkComputer/EmbeddedController/blob...
I've noticed that I seem to miskey my unlock password immediately after resuming from sleep way more often than when I use that password at other times, or when using an external keyboard (Lenovo T480). I always suspected that something was wonky, but a weird debounce bug would totally explain it, especially as I tend to type that password very quickly.
Testing was done [0], but it's not written in an easy-to-understand way. As a summary, Thinkpad keys are scrambled within 15-23 ms. Usually, humans ascribe scrambled letters to their own mistakes, but this time it's the keyboard's fault. Lenovo continues to ignore the issue.
One very stupid solution for your password is to change its letters to go from right to left. That way the scrambling will become anti-scrambling and you can type your password even faster than on a normal keyboard!
Re: Open-Sourcing our Firmware
#208I've been so happy to see what Framework has been doing lately, and really want to support them, but I already have a desktop as my primary computer and two Thinkpads that are already set up nicely, but that I rarely use. I moved from 15" laptops to 14" when Lenovo added the numpad on the larger variant, and 14" is about as small as I want to go. I kind of want to buy a framework though, just to support them? But I h…
Can anyone recommend a laptop that gets great battery life on Linux and has a good keyboard? I've been thinking about selling my current beefy laptop (razer blade 15) since I end up doing all my MCAD/ECAD work on my desktop anyway, and moving back to Manjaro on my laptop which only really gets used for software/firmware anyway. But, I read so many horror stories about linux firmware glitchyness and poor battery life…
It should be said I run a pretty minimal system (dwm, st, Vim, stuff like that) and usually throttle the system to "powersave", mostly because the fans will never spin up with it. It's a bit slower, but still plenty fast enough for me.
Re: Open-Sourcing our Firmware
#209Upsides:
- Hardware feels VERY premium and nice. It's not too heavy. You'd never guess it's the first laptop made by a new company.
- Keyboard is a pleasure to type on. I did nanowrimo last year on it and wrote ~60k words and never had a complaint.
- Company and its mission are awesome! Support team is very helpful and their communication has been great.
- Guides on the website for opening it up and replacing/fixing parts is amazing. If anything I hope I can keep this thing running for many many years.
- Choosing what ports you want via the expansion cards is really nice (USB-C charging on BOTH sides of the laptop?!?! amazing)
Downsides:
- Battery could be better. I get probably 3-6 hours on Win11 depending on what I'm doing.
- It can get HOT. I have the i7 processor; doing light dev work with a few Docker images running and VSCode with a medium-sized Node project open, it gets uncomfortably warm on my lap and the fan occasionally spins up. I played through Inscryption on it (awesome indie game, built in Unity) and the fan was EXTREMELY loud during the whole thing because it was making heavy work of the integrated graphics card. Just browsing the web or watching videos it is cool and silent, though.
- Because of issues with Tiger Lake, S3 sleep isn't supported so if it sleeps when you close the lid, the battery will continue to drain for a bit and eventually it'll go into hibernation. I set mine to just go into hibernation when the lid is closed which saves the battery more if I'm on-the-go. It takes around 11 seconds to wake from hibernation which isn't bad. Not an issue with the Framework specifically, I think this affects all Tiger Lake processors.
- Expansion cards are a bit of a novelty for me. I have 2x USB-C, 1x USB-A, 1X HDMI and don't see myself changing that any time soon and can't really think of any expansion cards I'd need in the future.
Looking forward the question at the top of my mind is "will this actually be upgradeable?"... if they ever release AMD or ARM-based processors, it'd be great to try them out, but you'd have to swap out the whole mainboard which is a bummer (but understandable given the hardware constraints). Different screen sizes would require a whole new laptop but at least you could bring along the internals. A touch screen would be really nice.
Re: Open-Sourcing our Firmware
#210Earlier quoted context omitted.
I very much wanted to hear about this and damn :-( Video playback must be hardware accelerated by now and be super efficient. Another worry was about low power sleep modes and waking up, and looks like it is not solved too. I might have to suck it up and buy the Mac for my needs after all. I have my trusty Linux desktop for all my big compute needs. I was hoping to make the mobile machine also run Linux, but the spec…
It's still a real pain to get hardware accelerated video in a browser on Linux. Google is still outright refusing to support it in chromium, even though they do support it inside Chrome OS. There are few community patches floating around if you're willing to roll your own chromium to enable to Chrome OS hardware decode pathways on generic Linux. You can mostly get it working on Firefox if you play around with the con…