HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
lenovo
lenovo-wwan-unlock
Shell2025–2025
lenovo / lenovo-wwan-unlock

lenovo-wwan-unlock

FCC and DPR unlock for Lenovo PCs

3Distinct people
3Mentions
1Explicit recommenders
154GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

FCC and DPR unlock for Lenovo PCs

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

What I love about Lenovo besides PSRef and all the maintenance/repair manuals (with part numbers, so that you know what to get if something needs to be replaced), etc. is that…

microtonal used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2025-07-27 15:21:40 UTC to 2025-12-25 16:30:05 UTC. Weeks start Monday, UTC.

012025-07-21 00:00:00 UTC to 2025-07-28 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 212025-07-28 00:00:00 UTC to 2025-08-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-04 00:00:00 UTC to 2025-08-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-11 00:00:00 UTC to 2025-08-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-18 00:00:00 UTC to 2025-08-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-25 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-08 00:00:00 UTC to 2025-09-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-15 00:00:00 UTC to 2025-09-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-22 00:00:00 UTC to 2025-09-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-29 00:00:00 UTC to 2025-10-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-06 00:00:00 UTC to 2025-10-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 62025-10-13 00:00:00 UTC to 2025-10-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-20 00:00:00 UTC to 2025-10-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-27 00:00:00 UTC to 2025-11-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-03 00:00:00 UTC to 2025-11-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-10 00:00:00 UTC to 2025-11-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-17 00:00:00 UTC to 2025-11-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-24 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2025-12-08 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-12-08 00:00:00 UTC to 2025-12-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-15 00:00:00 UTC to 2025-12-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-22 00:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 22

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 212025-07-21 00:00:00 UTC2025-07-28 00:00:00 UTC101
Jul 282025-07-28 00:00:00 UTC2025-08-04 00:00:00 UTC000
Aug 42025-08-04 00:00:00 UTC2025-08-11 00:00:00 UTC000
Aug 112025-08-11 00:00:00 UTC2025-08-18 00:00:00 UTC000
Aug 182025-08-18 00:00:00 UTC2025-08-25 00:00:00 UTC000
Aug 252025-08-25 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 12025-09-01 00:00:00 UTC2025-09-08 00:00:00 UTC000
Sep 82025-09-08 00:00:00 UTC2025-09-15 00:00:00 UTC000
Sep 152025-09-15 00:00:00 UTC2025-09-22 00:00:00 UTC000
Sep 222025-09-22 00:00:00 UTC2025-09-29 00:00:00 UTC000
Sep 292025-09-29 00:00:00 UTC2025-10-06 00:00:00 UTC000
Oct 62025-10-06 00:00:00 UTC2025-10-13 00:00:00 UTC000
Oct 132025-10-13 00:00:00 UTC2025-10-20 00:00:00 UTC000
Oct 202025-10-20 00:00:00 UTC2025-10-27 00:00:00 UTC000
Oct 272025-10-27 00:00:00 UTC2025-11-03 00:00:00 UTC000
Nov 32025-11-03 00:00:00 UTC2025-11-10 00:00:00 UTC000
Nov 102025-11-10 00:00:00 UTC2025-11-17 00:00:00 UTC000
Nov 172025-11-17 00:00:00 UTC2025-11-24 00:00:00 UTC000
Nov 242025-11-24 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 12025-12-01 00:00:00 UTC2025-12-08 00:00:00 UTC101
Dec 82025-12-08 00:00:00 UTC2025-12-15 00:00:00 UTC000
Dec 152025-12-15 00:00:00 UTC2025-12-22 00:00:00 UTC000
Dec 222025-12-22 00:00:00 UTC2025-12-29 00:00:00 UTC101

What Hacker News says

3 sources
I've been using ThinkPads with Linux since the T410, T420, T430, T480s, and several others. For me, they've consistently delivered an "everything works out of the box" experience with Ubuntu and/or Fedora, including things like SmartCard readers. I'm currently on a Lenovo X13 Gen 6 (AMD), and the only component that required any tinkering was the 5G WWAN due to FCC unlock issues (see: https://github.com/lenovo/lenovo-wwan-unlock/issues/68 ). One thing many people don't realize is that some Lenovo models can be ordered with Fedora pre-installed. That's a pretty strong signal for Linux compatibility. I've been watching Framework for years, and among my Linux-using colleagues we have ThinkPads, Frameworks, and Tuxedo machines, so comparisons are easy. I really want to like Framework, but recurring firmware issues, noise (!!), and the lack of
Read the rest
built-in 4G/5G antennas have pushed me toward Lenovo every time. That said, I do like the modular idea. I even use a small USB-C adapter permanently to protect the port from wear, almost all docking/monitor issues I've seen over the years came down to worn cables or ports. In that sense, Framework's modules are genuinely appealing.
In I'm returning my Framework 16
> Any one of us here could learn the skills to design a smartphone. Unless you're Fabrice Bellard who literally created a 4G softmodem - no. It takes a whole lot of people (or, again, one genius Fabrice Bellard clone) to design a smartphone. You'll need AT THE VERY LEAST: 1) a SoC that has reasonably open device drivers and specifications - without that, all attempts are moot 2) a hardware engineer to deal with the PCB 3) a low-level system engineer to deal with the initial bringup (aka, porting u-boot and maintaining it) 4) an RF engineer to deal with the black magic that is designing ultra high performance PCBs that deal with the RF stuff (2G-5G phone networks, BT, WiFi, NFC, GPS) and high-frequency buses (storage, RAM, baseband, USB, PCIe, CSI/DSI) 5) a GPU driver engineer of the class of Alyssa Rosenzweig to get the GPU drivers to beh
Read the rest
ave (she literally provided better-compliant drivers than Apple) 6) a battery engineer to ensure you don't end up with something like the ill-fated last Galaxy Note (that had to be fully recalled due to battery issues) 7) a ton of software engineers to get the basic things running that people expect from a smartphone (e.g. phone calls, 911, SMS, MMS, a browser and enough userland libraries so that third-party developers can begin to port games) 8) hosting engineers that deal with reliably delivering OS updates, application updates and A-GPS data 9) a skilled purchase and finance department to acquire all components as well as skilled QA people to make sure you don't get screwed in your supply chain by someone cutting corners or trying to engage in outright fraud 10) plastics and metal design engineers for the housing and other related engineering, and you'll probably also need engineers specializing in mass production and assembly as injection molding is a skillset on its own 11) engineers specializing in low power domains to get something that doesn't eat through the entire battery in a matter of hours 12) UX, UI designers to get something people can actually use (partially, that's also compliance stuff - think of accessibility laws) 13) testers to test your device against an insane load of other things - headsets, headphones, consumer and enterprise wifi, car head units, mice/keyboards, game controllers, USB hubs, monitors, projectors, adapters, dongles, IPv6 in its various abominations, phone network-side vendors, how devices behave in trains, cars, airplanes, cruise ships, in temperature and humidity extremes, under water, in back pockets (bending!), in dirt, dust, rain, being drenched in all kinds of beverages, muck, snow, fog, right next to extremely powerful broadcast radio transmitters, high magnetic/electric fields, teeth both human (toddlers) and animal (cats and dogs)... 14) logistics experts to deal with shipping, returns, refunds, recalls 15) customer support 16) psychoacoustics and acoustics engineers to make sure your device doesn't sound like shit (both what you hear, and that includes safeguarding the speakers from burning out, and what others hear from you, aka the beamforming stuff that the Asahi people reverse engineered) 17) video/colorspace engineers to make sure the whole darn thing isn't off color 18) camera/optics engineers, even if you acquire camera units these need to be integrated properly 19) lawyers and domain experts to deal with the compliance crap: RoHS, CE, FCC, India's regulatory authority, licensing, binary blobs, video codecs, audio codecs, carrier compliance testing, HDMI, HDCP, the RF compliance crap that's needed for US compliance [1], tariffs, sanctions laws... the list is endless 20) advertising (although admittedly, word-of-mouth could be sufficient), and PR in general (including websites, print media, AtL/BtL marketing) 21) deals with app developers, lest you end up like Windows Mobile 22) security testers/experts to make sure your devices don't get 0wned by cellebrite, mossad, nsa, cia, ... 23) human resources experts ("people engineers") to herd all the cats 24) packaging engineers to make sure the product arrives at the customer's hands both looking appealing and undamaged (tbh, that's at least four distinct skillsets as well) You're looking at a minimum of 2-4 million $ for the engineers alone, another 4-5 million $ for the compliance crap, many millions for the app deals and way more in upfront cash for components and logistics chains. That's why every attempt at a reasonably open source phone design has either failed or is many years behind the mass market. And the list of organisations attempting to do so include household names of the likes of Mozilla. And that is also why/how ODMs exist... they all have figured out some "minimum viable design" that gets tweaked a bit for the customer brand, and that's it. Everyone else went bust. Including, as mentioned, Microsoft. Including former powerhouses such as HTC. It's simply too complex to keep up. On HN, we could probably drum together people of all these skillsets, no doubt (it took me half an hour to think of all these people and I'm pretty certain I've missed important aspects still!), and even ones with enough money to burn. But even then: the competition are the richest companies on the planet: Apple, Google, Samsung. Good luck... (And yes: a minimum viable phone - probably a lot of people here including myself could whip that up using a COTS 5G modem, a Raspberry Pi and a power bank. But that's a MVP, not something you can sell to anyone less nerdy than Richard Stallman, and it's based off of the work of a lot of the people I just spent 58 minutes to think of and write down) [1] https://github.com/lenovo/lenovo-wwan-unlock
In GrapheneOS is the only Android OS providing full security patches
microtonal·Jul 27, 2025Recommendation phrase
What I love about Lenovo besides PSRef and all the maintenance/repair manuals (with part numbers, so that you know what to get if something needs to be replaced), etc. is that they often certify laptops for Linux. They also seem to really care about supporting Linux. E.g. WWAN modems need proprietrary unlock procedures these days thanks to the FCC [1]. Most vendors would shrug and say 'sorry, we only support Windows', Lenovo has a repo with Linux support for all the modems that ThinkPads support (you can only use supported modems, because the FCC apparently only certifies laptop/modem combinations, not individual modems): https://github.com/lenovo/lenovo-wwan-unlock [1] https://modemmanager.org/docs/modemmanager/fcc-unlock/
In Linux on Snapdragon X Elite: Linaro and Tuxedo Pave the Way for ARM64 Laptops

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.