chromebook-bug-could-reveal-location-history-from-guest-mode

Chromebook bug could reveal location history from Guest mode

A little-known behavior in Chrome OS could reveal a user’s movements through Wi-Fi logs. Leveraging Chrome OS’s Guest mode feature, the attack would require physical access to the device, but it can be executed without knowing the user’s password or having login access.

The bug was flagged to The Verge by the Committee on Liberatory Information Technology, a tech collective that includes several former Googlers.

“We are looking into this issue,” said a Google spokesperson. “In the meantime, device owners can turn off guest mode and disable the creation of new users.” Instructions for turning off Guest browsing are available here.

The bug stems from the way Chromebooks treat their Wi-Fi logs, which show when and how a computer connects to the broader internet. The logs can be confusing for nontechnical users, but they can be deciphered to reveal which Wi-Fi networks were in range of the computer. Combined with other available data, that could reveal the owner’s movements over the period of time covered by the logs — potentially as long as seven days.

Because Chrome OS keeps those logs in unprotected memory, they can be accessed without a password. Simply opening a Chromebook in Guest mode and navigating to a standardized address will bring up the logs in local storage. That will show all logs for the computer, even ones generated outside of Guest mode.

Electronic Frontier Foundation researcher Andrés Arrieta confirmed the attack and said it was of particular concern for targeted and marginalized communities. While the bug wouldn’t be useful to conventional cybercriminals, it’s a potentially devastating privacy issue for those worried about surveillance from family members or co-workers.

“It’s worrisome because anyone with quick physical access to the device could potentially get in as guest and quickly take some logs, and out details of location,” said Arrieta. “Security teams should try to better understand the potential repercussions of those bugs for all their users and include that in their assessment and prioritization of bugs.”

privacy-and-ads-in-chrome-are-about-to-become-flocing-complicated

Privacy and ads in Chrome are about to become FLoCing complicated

Illustration by Alex Castro / The Verge

Google is forging ahead with its third-party cookie replacement technology

Repent, o ye ad trackers, for the cookiepocalypse is nigh!

If Google sticks to its roadmap, by this time next year Chrome will no longer allow websites to use third-party cookies, which are cookies that come from outside their own domains. The change theoretically makes it vastly more difficult for advertisers to track your activities on the web and then serve you targeted ads. Safari and Firefox have already blocked those cookies, but when it comes to market share, Chrome is currently the leader and so its switchover is the big one.

Blocking third-party cookies means that only websites you explicitly visit will be able to save those little cookie files on your computer, and they should theoretically only do what cookies were originally intended to do: keep track of smaller things like whether you’re logged in or which shopping cart is yours. Blocking third-party cookies also means ad networks can’t figure out who you are and serve you targeted ads, which is a big problem for the ad industry.

Google, which is the biggest player in online ads, has claimed that it does not intend to replace third-party cookies with “alternative identifiers to track individuals as they browse across the web.” This seems like a win for privacy all around, but if something about the story of Google as the privacy and anti-ad crusader strikes you as a little… off, you are far from alone.

Because of course Google doesn’t want to kneecap the online ad industry — the one it dominates and from which it makes all its money. Instead, Google wants to replace the third-party tracking cookie with a complicated set of (bird-themed) technologies that are meant to let ad companies target specific demographics like age and location, while at the same time allowing the people who are targeted to remain anonymous.

Google is trying to avert the cookiepocalypse for the ad tech industry, no repentance necessary.

And so today, the company is forging ahead with an “origin trial” for one of these new technologies, the Federated Learning of Cohorts (FLoC). In an origin trial, websites are able to begin testing without asking browser users to turn on specific flags. The feature itself will be slowly turned on inside Chrome via the usual process of introducing it into developer builds, then beta, then finally in the shipping version most people use.

But what the hell is FLoC, and does it really protect your privacy?

FLoC: a Federated Learning of Cohorts

FloC is a proposed browser standard that, in Google’s words, will enable “interest-based advertising on the web” without letting advertisers know your identity. Instead, you’ll be associated with a “cohort,” a group of users sufficiently large enough to make you at least semi-anonymous to the companies targeting you.

That’s the simple explanation. The technical one gets very complicated very quickly. Here’s a quick version. Chrome browsers will use algorithms (the “Federated Learning” part) to create a very large number of “cohorts,” groups of people that share certain qualities and interests. Each person’s individual browsing history is kept private and never shared with anybody, but the browser itself will look at the history and then assign a user to one of those cohorts.

When you visit a website, Chrome will tell that site that the visitor is part of cohort 198273 (or whatever) and then it’s up to the website to know that cohort 198273 (or whatever) is interested in pickup trucks and shoes with vegan leather. Since Chrome will never assign a user to a small cohort (Google has proposed that it will wait until there are “thousands” in a group), your identity as an animal-loving coal roller is theoretically protected.

Chrome itself isn’t assigning any content labels to these FloCs; Google is leaving that to the ad tech industry to figure out. So you won’t be able to open up a privacy page inside Chrome and see what it thinks you’re interested in (though there’s theoretically nothing stopping a third-party website from telling you).

Since FLoC is structured in this way, it could mean that the powerful players in ad tech could become even more entrenched, because they have the technology to parse what FLoCs mean and what ads to target against them. Or it could mean smaller players could find a way in. We don’t know all the possible repercussions of FLoC, which is why it has both ad industry executives and privacy advocates so unsettled.

You can read the whole proposal and even check out the code for how it works at the GitHub repository for FLoC inside the Web Incubator Community Group. As with most things on the web, it’s being developed out in the open and is part of a process of proposals, critiques, counter-proposals, attempts to get other browser vendors to join, arguments, harangues, screeds, and good-faith efforts to make the web a better place. It’s a party, y’all.

The new front in the browser wars: privacy

No other browser vendor has signaled its intention to support FLoC. The rest are simply blocking third-party cookies and letting the chips fall where they may. And those chips are messy.

Whatever motivations you want to imbue on the Chrome team, it is already apparent that simply blocking third-party cookies will lead to very problematic new solutions from the ad tech industry. So Google is creating both FLoC and a suite of other technologies to replace the third-party cookie, in order to hopefully forestall even worse replacements.

One of the very bad things Google is trying to forestall is fingerprinting. That’s the generalized term for ways that websites can identify you through little data signals that leak out of your browser when you visit a site. Sites can look at your IP address, the OS you’re browsing from, the size of your window, whether your browser supports Bluetooth controllers, and much more.

Battling fingerprinting is a huge arms race for browser engineers and new, nefarious methods pop up seemingly weekly. Here’s a new method of fingerprinting I just came across: playing a very tiny bit of audio and then analyzing how your particular browser and device handle it, and then using that data to individually identify you in milliseconds. (The website that proposed it sells fingerprint services to legitimate companies so they can ostensibly use it to better identify potential fraudsters on their sites.)

Apple has very publicly and vociferously advocated for cutting off all methods of individualized tracking, including fingerprinting, and has committed itself to that arms race indefinitely. The Chrome team’s concern is that essentially such a hard line creates an incentive for legitimate ad tech companies to start engaging in fingerprinting, which will then be all but impossible to stop or regulate.

Here’s how Google puts it in its blog post:

When other browsers started blocking third-party cookies by default, we were excited about the direction, but worried about the immediate impact. Excited because we absolutely need a more private web, and we know third-party cookies aren’t the long-term answer. Worried because today many publishers rely on cookie-based advertising to support their content efforts, and we had seen that cookie blocking was already spawning privacy-invasive workarounds (such as fingerprinting) that were even worse for user privacy. Overall, we felt that blocking third-party cookies outright without viable alternatives for the ecosystem was irresponsible, and even harmful, to the free and open web we all enjoy.

It’s hard to separate each company’s financial incentives from their very real philosophical differences. Google prints money with its de facto monopoly on monetizing the open web through ads and is therefore incentivized to keep it going. At the same time, Chrome’s developers are true believers in the power and importance of the open web. Meanwhile, Apple wouldn’t be sad if Google made less money amid a massive online ad tracking reckoning. At the same time, Apple’s developers are true believers in the importance of personal privacy and the urgent need to go all-out in protecting that privacy against constant online assaults.

In any case, the problem with fingerprinting is that once you’re identified, it’s much harder to anonymize yourself. A cookie can be deleted, but the way your particular computer processes a milliseconds-long snippet of audio is much harder to change (though Brave has an innovative solution called Farbling).

The basic argument from the Chrome team is that erecting a so-called “privacy wall” will entice legitimate ad tech companies into succumbing to the temptation of fingerprinting. Google is hoping that ad tech companies will adopt FLoC as an alternative.

If nothing else, there’s one big thing to take away from all this: FLoC is a hell of a lot better than the current status of third-party cookies that directly identify you anywhere you go on the web. But “better than the worst” is a low bar, and it’s hard to know yet whether FLoC just clears it or vaults way over it.

Is FLoC really private?

Instead of a trying to build a metaphorical privacy wall that blocks all forms of ad targeting, Google plans on building a Privacy Sandbox inside Chrome. Within that sandbox, websites can still legitimately request to know certain details about your browser as they need. A game streaming site could ask to know if your browser supports a game controller, for example. But ask too much and you’ll exceed the browser’s “privacy budget” and get cut off. Websites can have just a little identifying information, as a treat.

FLoC will be part of that privacy sandbox and further should protect your identity by only associating you with a cohort if that cohort is sufficiently large. Chrome will also change what FLoC cohort your browser is associated with on a regular basis, say once a week or so.

But whether FLoC is actually anonymous is very much up for debate. Bennett Cyphers at Electronic Frontier Foundation recently put up a handy post detailing some of the biggest concerns with FLoC.

One of the key aspects of FLoC is that Google isn’t making some giant list of interests and demographics and then assigning you to them. Instead, it’s proposing to use Federated Learning to create a ton of these cohorts algorithmically. Chrome won’t really know what any of them are actually about; it’ll be up to ad tech vendors to understand that over time.

But as Cyphers points out, that algorithm will inevitably create cohorts that could be incredibly dangerous — say, a group of people who have visited sites about getting out of domestic abuse situations. The Chrome team says it recognizes this concern and so will be analyzing the algorithmically created cohorts to see if any are related to what it deems to be sensitive topics — and then Chrome won’t serve those cohort IDs. But FLoC isn’t centralized, so it’s important to know that if another browser vendor adopts FLoC, it will be incumbent on that browser to create similar block lists.

Websites will be able to opt out of participating in FLoC, meaning that visits to their sites won’t contribute to an individual FLoC user’s profile. Similarly, the Chrome team intends to put opt-out toggles somewhere in Chrome’s settings for users who don’t want to provide FLoC IDs to the websites they visit.

Could FLoC become just another data point for fingerprinters? It seems likely, and defending against that seems to be another job for Chrome’s privacy budget and privacy sandbox algorithms.

One more thing: FLoC is a very convenient way for the websites you visit to know enough about you to target relevant ads, which means that FLoC is a very convenient way for websites to know things about you. It’s certainly no worse than the current cookie situation, but it’s far from the “You Shall Not Pass!” philosophy other browser vendors (like Apple and Brave) apply to allowing access to potentially identifiable information.

What’s next?

This first FLoC “origin trial” is designed to help websites learn how FLoC works; some of the testing for Chrome users will come later. Here is how Google describes the way it’s going to work:

The initial testing of FLoC is taking place with a small percentage of users in Australia, Brazil, Canada, India, Indonesia, Japan, Mexico, New Zealand, Philippines and the U.S. We’ll expand to other regions as the Privacy Sandbox expands globally. In April, we’ll introduce a control in Chrome Settings that you can use to opt out of inclusion in FLoC and other Privacy Sandbox proposals. In the meantime, if you’ve chosen to block third-party cookies, you won’t be included in these origin trials.

If you look at that list of countries, you might notice that something stands out: none of them are in the EU, where GDPR regulations are in effect. Recently, Robin Berjon of The New York Times wondered whether that meant that FLoC would run afoul of those privacy regulations. According to the product manager for the Chrome privacy sandbox, Marshall Vale, it’s more a matter of limiting the size of the early tests and that his team is “100% committed to the Privacy Sandbox in Europe.”

Under normal circumstances, a newly proposed web technology wends its way through mailing lists and W3C conference room debates. It gets supported by the browser vendor that championed it and then, if its lucky, other browsers. Thus, the web manages to not become browser-specific in the ways it was back in the bad old days of Internet Explorer 6.

But when Google originally announced its intention to block third-party cookies last year, I pointed out that the rhetoric between browser vendors was getting sharp. It’s only gotten sharper as Apple, Google, Microsoft, Mozilla, Brave, and others have gone further down their respective paths.

It seems unlikely that FLoC will lead to a standard because everybody agrees on a good way to allow targeted advertising. If FLoC does become a standard, it’ll probably be because Chrome will eventually turn it on and it will become the norm just through sheer market share — both Chrome’s within the browser market and Google’s within the ad tech market.

That possible future might avert the cookiepocalypse, but it could also become a different kind of nightmare for the web: one where websites once again try to push you to use the browser they can best monetize via whatever ad tech platform they’re using.

samsung-galaxy-z-fold-2-vs-xiaomi-mi-mix-fold-vs-huawei-mate-x2:-what’s-the-difference?

Samsung Galaxy Z Fold 2 vs Xiaomi Mi Mix Fold vs Huawei Mate X2: What’s the difference?

(Pocket-lint) – Huawei’s second generation of its foldable smartphone comes in the form of the Mate X2, while Xiaomi’s foldable phone is called the Mi Mix Fold.

Both follow a similar design to the Samsung Galaxy Z Fold series after Huawei changed the format of the folding device from its predecessor – the Mate X and Xs- moving from a foldable display on the outside, to an inward folding display. 

If you’re in the market for a vertically folding smartphone, here is how the Xiaomi Mi Mix Fold, Huawei Mate X2 and the Samsung Galaxy Z Fold 2 compare.

Design

  • Mi Mix Fold: 173.3 x 133.4 x 7.6mm unfolded / 173.3 x 69.8mm x 17.2mm folded / 317g (Black) 332g (ceramic)
  • Mate X2: 161.8 x 145.8 x 4.4-8.2mm unfolded / 161.8 x 74.6 x 13.6-14.7mm folded / 295g
  • Z Fold 2: 159.2 x 128.2 x 6.9mm unfolded / 159.2 x 68 x 16.8mm folded / 282g

The Xiaomi Mi Mix Fold has a vertical folding display in a book-style design, like the Huawei Mate X2 and Galaxy Z Fold 2. It comes with a glass or special edition ceramic back and there is a prominent camera housing in the top left corner. There’s a metal frame, large display and a single punch hole camera in the top right corner when folded.

When unfolded, the Mi Mix Fold has an 8.01-inch display and a precision based hinge. There is a small gap when folded though, like the Samsung Galaxy Z Fold 2. It comes in Black or Special Edition Ceramic finishes.

The Huawei Mate X2 meanwhile, also features a vertical folding display. There’s a glass rear with a prominent rectangular camera housing in the top left corner, a metal frame and a full display with dual cut-out cameras on the front when folded. 

When unfolded, the Mate X2 has a large 8-inch screen. The hinge is multi-dimensional, creating a water dropped-shaped cavity for the display when the phone is folded, allowing for no gap at all when shut, resulting in a different design to the Mi Mix Fold and Galaxy Z Fold 2. There’s also a wedge-like design that is just 4.4mm at the slimmest point. It comes in White, Black, Crystal Blue and Crystal Pink colours.

The Samsung Galaxy Z Fold 2 has a similar form to the Huawei Mate X2 and Xiaomi Mi Mix Fold in that it offers a vertical fold in a book-style design. It too has a glass rear, with a rectangular camera housing in the top left corner, as well as a metal frame. Like the Mi Mix Fold, it has a single, punch hole camera on the front when folded but it is centralised rather than positioned to the right.

When unfolded, the Galaxy Z Fold 2 has a slightly smaller 7.6-inch display than the Huawei Mate X2 and Xiaomi Mi Mix Fold. It’s hinge allows for multiple viewing angles but there is a slight gap at the fold of the device when folded. It comes in Mystic Bronze and Mystic Black colours.

Display

  • Mi Mix Fold: 8.01-inch unfolded, 6.5-inch folded, OLED, 90Hz refresh rate
  • Mate X2: 8-inch unfolded, 6.45-inch folded, 8-inch unfolded, OLED, 90Hz refresh rate
  • Z Fold 2: 7.6-inch unfolded, 6.23-inch folded, OLED, 120Hz refresh rate

The Xiaomi Mi Mix Fold has a 6.5-inch AMOLED display with a resolution of 2520 x 840 resolution and a pixel density of 409ppi on the front when folded. It has a 27:9 screen ratio and a 90Hz refresh rate. There’s a punch hole camera in the top right, and the bezels are slightly larger than the Huawei and Samsung alternatives. 

When unfolded, the Mi Mix Fold has a 8.01-inch display WQHD+ resolution, 1 billion colours and a 4:3 aspect ratio. It has a 60Hz refresh rate.

The Huawei Mate X2 has a 6.45-inch OLED display with resolution of 2700 x 1160 and a pixel density of 456ppi on the front when folded, making it fractionally smaller than the Mi Mix Fold, though with slimmer bezels. It features a 21:9 aspect ratio and a 90Hz refresh rate. As mentioned above, the X2 has dual punch-hole front cameras in the top left of the display.

When unfolded, the Mate X2 has an 8-inch OLED display with a 2480 x 2200 resolution, which results in a pixel density of 413ppi. The unfolded display has a ratio of 8:7.1. It too has a 90Hz refresh rate.

The Samsung Galaxy Z Fold 2 has a 6.23-inch external display, making it slightly smaller than the Mate X2 and Mi Mix Fold. It too is an AMOLED panel and it offers a resolution of 2260 x 816 pixels and an aspect ratio of 25:9. 

When unfolded, the Galaxy Z Fold 2 has an internal display of 7.6-inches – which is the smallest of the three devices being compared here. It’s Dynamic AMOLED and it has a 2208 x 1768 pixel resolution, resulting in a pixel density of 372ppi. It also has a 120Hz refresh rate and supports HDR10+.

Cameras

  • Mi Mix Fold: Triple rear camera (108MP + Liquid Lens 8MP + 13MP), 20MP front
  • Mate X2: Quad rear camera (50MP+16MP+12MP+8MP), 16MP front
  • Z Fold 2: Triple rear (12MP+12MP+12MP), 10MP front

The Xiaomi Mi Mix Fold has three lenses on its rear, with a 108-megapixel main sensor with 2.1µm pixels and a 7P lens, along with a 13-megapixel ultra wide angle lens with a 123-degree field of view.

There is also an 8-megapixel liquid lens on the rear that uses the principle of human eye bionics and a special chip created by Xiaomi to change the radius of curvature of the spherical surface. It allows the one lens to cover two functions, enabling 3x optical zoom, up to 30x digital and a minimum focus distance of 3cm. The front camera on the Mix Mix Fold is a 20-megapixel snapper. 

The Huawei Mate X2 has a quad camera on the rear, which features Leica technology, like Huawei’s other flagship smartphones. The camera setup includes a 50-megapixel main sensor, 16-megapixel ultra-wide angle sensor, 12-megapixel telephoto sensor, and an 8-megapixel SuperZoom sensor.

The main sensor has a f/1.9 aperture and OIS, the Ultra-wide sensor has a f/2.2 aperture, the telephoto sensor has a f/2.4 aperture and OIS with 3x optical zoom, while the SuperZoom sensor has a f/4.4 aperture, OIS and 10x optical zoom. The front camera is 16-megapixels wide angle with a f/2.2 aperture.

The Samsung Galaxy Z Fold 2 has a triple rear camera, comprised of a 12-megapixel main camera, 12-megapixel telephoto sensor and 12-megapixel Ultra-wide sensor.

The main camera has an f/1.6 aperture, dual pixel phase-detection autofocus and OIS, the telephoto lens has an aperture of f/2.4 and OIS and the ultra-wide sensor has an aperture of f/2.2. There is also a 10-megapixel front camera.

Hardware and specs

  • Mi Mix Fold: Qualcomm Snapdragon 888, 5G, 12/16GB RAM, 256/512GB storage, 5020mAh
  • Mate X2: Kirin 9000, 5G, 8GB RAM, 256/512GB storage, 4500mAh
  • Z Fold 2: Qualcomm Snapdragon 865+, 5G, 12GB RAM, 256/512GB storage, 4500mAh

The Xiaomi Mi Mix Fold runs on Qualcomm’s Snapdragon 888 chipset. It’s a 5G handset and it comes with 12GB of RAM and either 256GB or 512GB of storage. The Special Edition Ceramic model has 16GB of RAM and 512GB of storage though.

There’s a 5020mAh battery under its hood that supports Xiaomi’s 67W fast charging. The software is MIUI 12, based on Android 10 and there features like a one click option to close down things like GPS for security, as well as a Desktop Mode with a three-finger swipe.

The Huawei Mate X2 runs on Huawei’s own 5nm Kirin 9000 platform. It too is a 5G device. It is supported by 8GB of RAM and it comes in 256GB and 512GB storage variants.

It has a 4500mAh battery under the hood that supports Huawei’s 25W SuperCharge. Huawei’s own Harmony OS can be installed over the company’s usual EMUI interface running on top of Android.

The Samsung Galaxy Z Fold 2 runs on Qualcomm’s Snapdragon 865 Plus chipset, supported by 12GB of RAM and it comes in 256GB and 512GB storage options.

There’s a 4500mAh battery running the Fold 2, which supports 25W wired charging, 11W wireless charging and 4.5W reverse wireless charging. It runs Android with Samsung’s One UI over the top and there are some great multi-tasking features that make great use of the screen when unfolded. 

Price

  • Mi Mix Fold: Equivalent of £1105/$1550, China
  • Mate X2: Equivalent of £1985/$2785, China
  • Z Fold 2: £1799, $1999

The Xiaomi Mi Mix Fold costs RMB 9999, 10,999 or 12,999, starting at the equivalent of $1550 or £1105. It will be available in China from 15 April.

The Huawei Mate X2 costs RMB 17,999 or 18,999, starting at the equivalent of $2785 or £1985. It is available in China only for now. 

The Samsung Galaxy Z Fold 2 costs £1799 in the UK and $1999 in the US. 

SQUIRREL_339457

Conclusion

The Xiaomi Mi Mix Fold and Huawei Mate X2 is only available in the Chinese market at the moment but while the Mate X2 is a little more expensive than the Samsung Galaxy Z Fold 2, the M Mix Fold is cheaper.

On a spec-by-spec comparison, these three devices are similar and while the Xiaomi Mi Mix Fold tips the scales in several areas, the other two devices have their fair share of wins too.

The Xiaomi Mi Mix Fold has larger displays both interior and exterior than both the Huawei and Samsung. It also offers the most advanced Qualcomm chipset, the largest battery of the three devices, the fastest wired charging capabilities and it has an interesting camera setup with its liquid lens.

The Mate X2 arguably has a more streamlined design, an extra camera on the rear and a wide-angle front camera. It also has only fractionally smaller displays than the Mi Mix Fold.

The Galaxy Z Fold 2 has more RAM than the Mate X2 but the same as the Mi Mix Fold. It also has a higher refresh rate on the internal display though and it offers a more user-friendly software experience, as well as supporting Google services – the latter of which the Mate X2 does not offer. The Z Fold 2 has less cameras than Huawei but the triple rear camera does offer great results.

The Samsung is more widely available than both the Mate X2 and the Mi Mix Fold so while the Mi Mix 2 and Mate X2 might win on some specification areas, you’ll need to live in China to get your hands on them for now. It’s also worth remembering the Galaxy Z Fold 3 is tipped for a July 2021 launch.

Writing by Britta O’Boyle.

adafruit-demos-tiny-rp2040-board-ahead-of-release

Adafruit Demos Tiny RP2040 Board Ahead of Release

(Image credit: Adafruit)

Adafruit’s smallest RP2040 board is still coming soon, but in a recent video, Adafruit founder Limor “Ladyada” Fried demonstrated the QT Py 2040, a tiny board powered by the same chip as a Raspberry Pi Pico, using a community Arduino core that enables any RP2040 board to be used with the Arduino IDE.

In the video, we get a first look at Adafruit’s upcoming QT Py RP2040, which Fried mentions is being readied for sale. The QT Py RP2040 is shown running a simple temperature sensor project, with the board connected to an I2C OLED and temperature sensor via the Stemma QT connector. The QT Py 2040 is compatible with CircuitPython and the Arduino IDE via a community project, Arduino-Pico from Earle F. Philhower, III. Official Arduino support for the RP2040 is still a work in progress, possibly timed to coincide with Arduino’s own RP2040 board.

Adafruit has three RP2040 boards in their range. From their largest board, the Feather RP2040 which has already been released, to the IstyBitsy RP2040, to the QT Py RP2040, Adafruit has a board for all projects and wallets. Measuring just 22 x 18 mm, the QT Py RP2040 isn’t the smallest RP2040 board, that honor goes to Pimoroni’s Tiny 2040. But the QT Py packs plenty of features into a diminutive form factor.

  • USB Type C connector
  • RP2040 32-bit Cortex M0+ dual-core running at ~125 MHz @ 3.3V logic and power
  • 264 KB RAM
  • 4 MB SPI FLASH chip for storing files and CircuitPython/MicroPython code storage. No EEPROM
  • Native USB supported by every OS (USB HID)
  • Can be used with Arduino IDE or CircuitPython
  • Built-in RGB NeoPixel LED
  • 13 GPIO pins (11 breakout pads and two QT pads):
  • Four 12 bit ADCs (one more than Pico)
  • Two I2C ports (STEMMA QT and GPIO)
  • SPI and UART peripherals
  • PWM outputs on every IO pin
  • There are 6 GPIO in consecutive order for PIO compatibility
  • 3.3V regulator with 600mA peak output
  • Reset button and Bootloader buttons

The pricing and release date for the QT Py RP2040 is still largely unknown, with stock being prepared for their store we can expect an imminent release. At a guess, the price could be between that of a Raspberry Pi Pico ($4) and the Feather RP2040 ($12).