Author Archives: adachan

Illustration of a smartphone on a car dashboard showing a maps app with a sparkly AI assistant button.

Apple Makes Me Talk to Two Assistants. Google Put One in Maps.

Originally published on snarky.tech.

These days I use Grok Bot more than any other assistant. I still like having Gemini around, especially when I’m already in Google Maps.

What I don’t like is Apple’s official path to a different assistant. If I want ChatGPT from the system assistant on my iPhone, I have to go through Siri first. Siri, then ChatGPT. I call them double agents. It’s kind of a pain.

Illustration of a smartphone on a car dashboard showing a maps app with a sparkly AI assistant button.
An illustration of a smartphone on a car dashboard, with a maps app open and a sparkly AI assistant button on the screen.

Google’s workaround is a button in Maps. During navigation, you tap Gemini, or on the phone you can say “Hey Google,” and you’re talking to one assistant instead of two. That button is much faster than the double-agent routine for the same information.

What’s actually in Maps

On iPhone, once you’re navigating, the Gemini icon is there in the navigation screen. Google’s help pages say you can ask it to add a stop, avoid tolls, tell you when you’ll arrive, find a place along the route, or report traffic. You can also ask about a place, like when it closes or what’s popular on the menu.

That showed up for driving directions last year, and then for walking and cycling on iPhone wherever Gemini is available. (9to5Google)

In October, Google said the same button is coming to Google Maps navigation on CarPlay. You start a route, then tap the Gemini icon on the car display. The launch coverage said it was available in the U.S. first, with a global rollout underway. (9to5Google) That’s the version that matters in my Jeep, which does wireless CarPlay.

Google also started rolling out a standalone Gemini app on CarPlay in November. Different button, same idea: talk to Gemini without asking Siri first. (Google)

Why the button is there

On a U.S. iPhone, the system assistant is still Siri. Hold the side button, you get Siri. There isn’t a setting that lets me make Gemini, Grok, or ChatGPT the default.

Apple will let Siri hand a question to ChatGPT, if you’ve turned that extension on. Apple’s own examples start with “Hey Siri, ask ChatGPT…” That’s the official hook, and it’s ChatGPT, not a picker for the assistant I actually use. If you’re on Siri AI, you have to ask for ChatGPT before the request even goes out.

So the “Apple way” of getting a non-Siri answer is to talk to Siri so Siri can talk to ChatGPT. Two assistants, for a question I could have just asked.

Google can’t replace Siri on my phone. What it can do is put Gemini inside an app I already have open on the dash.

Bottom line

I use Grok Bot most of the time. I like having Gemini too. I just don’t want to go through two assistants to ask one question, not when a button in Maps will do.

Apple can keep the side button. Google put the shortcut in the map.

Illustration of a red Jeep Wrangler with the top down, photographed from the driver's seat so the dashboard touchscreen is visible.

I Turned Off My Jeep. My iPhone Is Still Talking to It.

Originally published on snarky.tech.

I park, turn the Jeep off, grab my stuff, and walk inside. Then I go to dictate a text on my iPhone 15 Pro Max and… nothing. Or worse, something, just badly, because my phone is still connected to CarPlay and is listening through the Jeep’s microphone. The Jeep is out in the driveway. I’m in the kitchen. Siri can’t hear me because Siri is sitting in the Jeep.

This is one of those problems where every piece is working exactly as designed, and the combined result is ridiculous.

Illustration of a red Jeep Wrangler with the top down, photographed from the driver's seat so the dashboard touchscreen is visible.
An illustration of a red Jeep Wrangler with the top down, with the dashboard touchscreen visible.

The setup

First, a detail that matters. My 2023 Wrangler’s Uconnect does CarPlay over a cable. Wireless CarPlay on most 2023 Wranglers comes from a little adapter plugged into the USB port, not from Jeep. People on the Wrangler forums found this out the same way I did, including one owner whose Jeep tech support rep insisted their 2023 had the newer Uconnect 5 with wireless CarPlay. It didn’t. (wranglerforum)

The adapter works great while I’m driving. The problem is what happens after I stop.

And it’s not one bad adapter. I’ve tried this with multiple wireless CarPlay adapters, and they all behave the same.

The Jeep doesn’t really turn off

The Wrangler’s USB ports stay powered after you shut the engine off. The manual says about 60 minutes. One owner on JLWranglerForums tested every USB port on two JLs and found they actually stayed on for about 65 to 75 minutes. (jlwranglerforums)

Then it gets better. Open any door and the timer starts over. If you have proximity entry, just touching a door handle starts it over. (jlwranglerforums) So if you go back out for the groceries, the dog leash, or the sunglasses you left on the dash, you’ve bought yourself another hour of a wide-awake CarPlay adapter. From where I’m standing, “about an hour” works out to “all the time.”

The adapter makers don’t pretend otherwise. Carlinkit’s own support page says its dongle “does not have a power switch function” and “will remain on as long as there is power output from the car’s USB.” (carlinkit) Ottocast says the same thing about its adapter, and its official fix is to turn off your phone’s Wi-Fi and Bluetooth or unplug the device. (ottocast)

Why my phone’s mic isn’t working

When an iPhone is connected to CarPlay, it uses the car’s microphone for Siri and voice. That’s what you want at 70 mph. It’s not what you want from your couch. (macrumors)

So the phone sees a powered-up CarPlay adapter nearby, stays connected, and routes my voice to a microphone that’s 40 feet away, behind a wall, inside a parked Jeep.

I’m not the only one

The Wrangler forums are full of this:

  • One owner parks near his office window and says that because the USB ports stay powered for nearly an hour, incoming calls jump to CarPlay and he has to switch them back to the phone. Another says his calls get routed to CarPlay just walking around the house or the garage. (jlwranglerforums)
  • Another owner has been on business calls where he was talking and talking while the other person’s audio played inside the Jeep, where he couldn’t hear it. He called Uconnect support. Their answer: turn off Bluetooth when you get out, and there’s “no way to disable” it. (jlwranglerforums)
  • Someone else realized YouTube had no sound on his phone because it was still playing to the adapter in the Jeep. (jlwranglerforums)

To be fair, not everyone sees it. In the same threads, other owners say their phone drops CarPlay as soon as the radio turns off, powered USB or not. That probably depends on the adapter, the firmware, and how close you park. Mine is close.

What I already tried

The usual advice is to change the radio-off delay or turn off “Allow CarPlay While Locked.” My Jeep doesn’t have a radio-off delay setting I can find. My iPhone’s CarPlay settings for the adapter don’t have an “Allow CarPlay While Locked” switch either.

Can you reprogram the USB timer? Longtime forum members say no Uconnect setting or programming tool changes it. They tested this on several JLs and a Gladiator. (jlwranglerforums, jlwranglerforums) One owner spotted a “USB Connection Presence” option in JScan but never tried it. (jlwranglerforums) I haven’t found anyone who has confirmed it changes anything.

What actually works

There’s no setting, so every fix I found is a workaround:

  1. Cut the adapter’s power. This is what most Wrangler owners land on. Put an inline USB cable with an on/off switch between the port and the adapter, and click it off when you get out. (jlwranglerforums) It works every time. It’s also one more thing to remember, which kind of defeats the point of wireless.
  2. Power the adapter from the 12V outlet. One owner found a splitter cable that runs data from the dash USB port and power from the 12V outlet, which shuts off when the vehicle does. When the Jeep turns off, the adapter turns off too, and “now I don’t care how long after I shut the car off the usb ports are still powered.” (jlwranglerforums) This is the closest thing to a real fix.
  3. Make the phone let go. Ottocast’s official advice is to turn off Wi-Fi and Bluetooth on the phone. (ottocast) You can automate that with a Shortcuts personal automation. One MacRumors user made a Home Focus that turns on when he arrives home, then has it run a shortcut that turns Wi-Fi off and back on. That kicks the phone off the adapter’s Wi-Fi. (macrumors) Shortcuts also has a “CarPlay Disconnects” trigger, but if the phone never thinks CarPlay disconnected, it won’t fire.
  4. Check the adapter’s own settings. Carlinkit adapters have an Auto Connect on/off switch in their settings page. (carlinkit) Turning it off probably also means connecting by hand when you get in. Jeep owners with the AAWireless Android Auto adapter say its app has a setting that disconnects the phone once Uconnect shuts down, and it works. (jlwranglerforums)

What I’m trying

I’m going with option 1. I ordered a 5.9-inch USB-A extension with an on/off switch that also passes data, so it can sit between the Jeep’s USB port and the adapter almost like a dongle. I’ll update this post once I’ve tested it.

Bottom line

The Jeep keeps its USB ports alive for an hour, and touching a door gives it another hour. The CarPlay adapter has no off switch. The iPhone uses whatever microphone CarPlay hands it. Every company involved can point at someone else, and Uconnect’s official answer is to turn off your Bluetooth.

Jeep, a “USB power off with ignition” toggle in Uconnect settings would fix this for everyone. Until then, the fix for my expensive Wrangler is a cable with a little on/off switch on it.

Illustration of a living-room TV showing a Roku-style home screen with a row of colorful app tiles.

YouTube TV Used to Autoplay Perfectly on My TCL Roku TV. Then Google Quietly Took It Away.

Originally published on snarky.tech.

It used to work perfectly. That’s the part I can’t get past.

I’d turn on the TCL Roku TV, open YouTube TV, and a live channel would already be playing. Usually the last one I’d been watching. No hunting around on the home screen, no extra clicks. It just started, the way a TV is supposed to start.

Then it stopped. The app opens to a dead, silent home screen. The “Autoplay on start” toggle is still sitting there, still set to on, and nothing happens. I have tried a lot of things. None of them brought it back.

Illustration of a living-room TV showing a Roku-style home screen with a row of colorful app tiles.
An illustration of a living-room TV showing a Roku-style home screen.

Two months ago I wrote about this as a mystery: the same setting worked every time on my Nvidia Shield, Apple TV, LG, PS4, PS5, and Xbox, and did nothing on several of my Rokus. I didn’t have an official explanation then. I do now, and it’s more annoying than a bug. Google didn’t break autoplay on this TV. They took it away, quietly, from hardware that used to have it.

I already ran the usual list. Twice.

I restarted the Roku. I power-cycled it at the wall. I checked for system and app updates. I turned Autoplay on start off and back on. I removed the YouTube TV app, restarted the Roku, and only then reinstalled it, which is the version of a reinstall that actually clears leftover settings. None of it mattered. The toggle stayed on. The home screen stayed quiet.

There is one gotcha that’s worth knowing about, because it is real, and because it is not a fix for this. A reply on the YouTube TV community forum points out that Autoplay on start only fires when you actually launch the app from a closed state. A lot of the time, turning the TV “off” just puts the Roku and the app to sleep. When you wake it up, you are resuming, not starting, so autoplay never runs. On a Roku, fully closing the app means highlighting YouTube TV on the home screen, pressing the star button, and choosing Close, then opening it again.

Try that once if you haven’t. If Google has already disabled the feature on your hardware, closing the app just gets you to the same silent home screen a little more honestly.

I’m not the only one, and it used to work for them too

This is not a one-off on my set. In October 2025, people were already in the YouTube TV forums saying autoplay was on and still didn’t work. One thread is literally titled “My autoplay is not working. How do i fix this?”

The same week, a Reddit thread described it the way I would have: YouTube TV had worked for years, and then, “out of nowhere, the autoplay function just stopped working.” Opening the app just went to the home screen. Nothing started. The setting was on. Restarts, a power cycle, even talking to Google support didn’t bring it back. (Reddit)

That pattern has kept showing up. People with multiple Rokus say it still works on one box and not on another. People say it used to autoplay on a given TV and then didn’t. In July 2026, a commenter on r/youtubetv put it plainly: YouTube TV “has intentionally removed certain features such as autoplay for older Roku devices.” (Reddit)

It wasn’t a bug. Google gated it

Here’s the explanation I didn’t have in September.

On that October 2025 “autoplay is not working” thread, a community product expert didn’t walk the person through another reset. They said a change had been made “recently” for older and less powerful devices, “mainly those with less than 512MB RAM,” and that “background play is no longer supported.” Memory, they pointed out, is not storage, and you cannot add more. The advice was to buy a newer standalone streaming device, “because your device has 512MB RAM or less” and “future features might not be included on your device.”

Google’s own help page is vaguer, but it points the same direction. Buried under the supported-device list is this line: “Select devices with 512mb or less of memory may have a slightly different experience and some features may not be available.” (YouTube TV Help)

I want to be precise, because these are not the same sentence. The expert replies usually talk about background play: the live video that keeps going behind the guide. What a lot of us noticed first is Autoplay on start: you open the app, and something is playing. Those look like two faces of the same cutoff, and they started being reported together. What I have not found is a Google page that says, on this date, we removed Autoplay on start from these TVs.

The closest public timestamps I can find are early October 2025, when those expert replies started going up, and Reddit posts from that same week from people saying the feature had died about a month earlier. That would put the first wave around September 2025. In June 2026, 9to5Google wrote about another wave of the same restrictions on Rokus, with reports starting in late May, including a Live guide that only shows 24 hours ahead. Google has not, as far as I can tell, published a dated announcement of its own.

I can’t tell you, from here, exactly how much RAM is in my TCL. Google doesn’t publish a model-by-model list. Plenty of Roku TVs shipped with 512MB or less, and if that’s the line, a television that used to autoplay is now on the wrong side of it. No setting I can flip will put it back.

The “fix” is to buy another box

The same expert replies come with a shopping list. If you want the feature back, get something newer: a Roku Streaming Stick 4K if you want to stay in the Roku world, a Fire TV Stick 4K Max, or a Google TV Streamer. They also mention a current Roku Ultra, an Apple TV 4K, and the Onn 4K Plus or Pro.

That would work. I already know it would work, because autoplay still works on the other boxes in this house.

Here’s what I can’t get past. The TCL still plays YouTube TV. The picture is fine. The app opens. The hardware did this exact thing, perfectly, until Google decided it shouldn’t. They didn’t put a notice on the screen. They left the toggle in the menu and turned the feature off.

I’ve written before about Google nagging me to replace hardware that still works. This is the same move, just quieter. A built-in Roku TV is supposed to be the box. The consolation prize is that I should go buy a stick, plug it into an HDMI port, and leave the smart TV I already paid for to sit there looking like a TV.

If that’s the line, say so on the help page, in the app, and on the toggle that still pretends to do something. Don’t make people restart, reinstall, and crawl through forums for a year only to find out the setting is decorative now.

Bottom line

If YouTube TV used to autoplay on your Roku TV and then stopped, you probably didn’t break a setting. Google appears to have pulled autoplay and background play from lower-memory devices, many of them Roku TVs, and the toggle can remain in the menu anyway. Fully closing the app with the star button is worth one try. After that, the only fix they will offer you is new hardware.

I’ll update this if Google ever bothers to document the cutoff, or if a software update gives the feature back to the TVs that already had it.

Illustration of an all-in-one touchscreen PC on a kitchen counter beside a cooktop, with a tortellini recipe on the screen.

Paprika 4 Is the Recipe App We Use Every Single Day

Originally published on snarky.tech.

We use Paprika Recipe Manager every single day. It lives on the touch-screen all-in-one PC on our kitchen counter, and it lives on our phones, and it syncs between them. When I add a recipe or check something off the grocery list in one place, it’s waiting in the other. After years of cooking this way, that simple habit is the reason we haven’t switched.

Illustration of an all-in-one touchscreen PC on a kitchen counter beside a cooktop, with a tortellini recipe on the screen.
An illustration of the kind of setup we have: a touch-screen all-in-one on the kitchen counter, close to the cooktop, with a recipe up on the screen.

A kitchen computer is only useful if it can run the app you actually cook from. Ours can. We leave Paprika up on that screen, walk up to it, and tap through a recipe while something is already on the cooktop. The phone is what we carry to the store. Same library, same lists.

Version 4, without the usual upgrade trap

Paprika 4 came out on November 6, 2026, for iOS, macOS, Android, and Windows. It’s a real upgrade. The interface is refreshed. There’s a cook mode for working through a recipe step by step, cookbooks for organizing the collection, separate pantry locations for the fridge, freezer, and cupboard, a better advanced search, and a duplicate finder. And on Windows, something a lot of us had been waiting for finally arrived: dark mode. Paprika can follow your Windows light or dark appearance, or you can set the theme yourself.

Version 4 also adds a premium subscription. Some of the new features sit behind it: importing recipes from TikTok, Instagram, Facebook, and YouTube; scanning a cookbook page or recipe card; family accounts; barcode scanning; nutrition labels; category suggestions; calendar feeds; clipboard importing; Alexa integration; and sending recipes directly to other Paprika users. According to Hindsight Labs’ announcement, Paprika 4 Premium is $14.99 a year in the U.S. (with a 7-day free trial), and existing users can get it for $9.99 a year. Prices can vary by region.

I think the yearly fee is a bit high. I’m not going to pretend otherwise.

Here’s what I appreciate most about how they handled the upgrade. If you already bought a previous version of Paprika, you are not locked out of Version 4 for deciding not to subscribe. You get a free upgrade to the standard version: unlimited recipes, cloud sync across your devices, the new interface, cook mode, cookbooks, pantry locations, advanced search, the duplicate finder, and the Windows dark mode. You also keep the features you already had in Paprika 3. Premium is optional. They keep letting you use the app with your previous license, without paying again.

It’s a great program

I can wish the new subscription were a little cheaper and still mean this completely: Paprika is a great program, and we use it every single day. If you cook at home and want your recipes on a kitchen screen and in your pocket, start at paprikaapp.com.

fNIRS motor-task activation for left- and right-hand finger-thumb tapping

Does fNIRS See What fMRI Sees? Our SfN 2026 Poster, Interactive

Next week I’ll be in Washington, D.C. for Neuroscience 2026, the Society for Neuroscience meeting, with a new poster from our lab: “fNIRS-fMRI Reliability for Motor and Social Perception Paradigms: Validation of fNIRS Against fMRI.” It asks a simple question that sits under almost everything we do: when fNIRS says part of the brain is active, does fMRI agree? Below is a plain-language summary and an interactive version of the poster you can click through.

The question

Our lab uses fNIRS (functional near-infrared spectroscopy), which measures hemodynamic, or blood-flow, responses with optodes placed on the scalp. Its big advantage is that it lets us study people in natural situations, including live, face-to-face interaction, which is exactly what developmental and social neuroscience needs. But fMRI is still the reference standard, and fNIRS needs to be checked against it systematically, on more than simple reference tasks. So we compared the two directly.

What we did

We used two calibrated benchmark tasks and ran each one with fNIRS (a Shimadzu LABNIRS system) and with fMRI (a Siemens MAGNETOM Prisma 3T).

  • Finger-thumb tapping. People tapped with the left hand or the right hand in 15-second blocks with 15 seconds of rest, for 6 minutes, with the same timing for fNIRS and fMRI. This is a focal test: it should light up primary sensorimotor cortex on the side opposite the hand.
  • Dynamic faces. People watched short videos of children’s faces smiling, moving and chewing (stimuli from Pitcher and colleagues, 2011). This targets the face network, especially the posterior superior temporal sulcus (pSTS), a region that is central to social perception.
fNIRS motor-task activation on the cortical surface for left-hand and right-hand finger-thumb tapping, with primary sensorimotor cortex (M1/S1) labelled
From the poster: fNIRS reproduces the left/right pattern of the motor task. Left panel, left-hand tapping; right panel, right-hand tapping.

What we found

For the motor task, fNIRS reproduced the hemispheric lateralization seen with fMRI: left-hand tapping drove the right primary sensorimotor cortex and right-hand tapping drove the left, with robust correspondence between the two methods.

For the face videos, both fNIRS and fMRI picked up the dynamic-face network, including multiple sites along the pSTS. fNIRS reliably detected activity in visual and lateral-occipital cortex and in the superior and middle temporal lobes, with high spatial correspondence to the fMRI BOLD signal. Overall, the two methods showed strong spatial agreement in both tasks.

We are also working on the depth question. Continuous-wave fNIRS sees superficial cortex, roughly half the distance between a source and a detector, while fMRI is fully 3D. Using one participant’s own fMRI and anatomical scans together with a NeuroDOT sensitivity model, we are building a pipeline to estimate how well fNIRS reaches the superficial and deeper parts of the fusiform face area and the pSTS.

Why it matters

In the scanner, social stimuli have to be recorded video, and that removes two things that define a real social exchange: a recorded face can’t return your eye contact, and it can’t react to or mirror your expressions. fNIRS has neither limit, so we can study live, face-to-face interaction with real two-way gaze and facial expression. Showing that fNIRS agrees with fMRI on these benchmarks supports using it in developmental settings where fMRI is impractical and where ecological validity really matters. The honest caveat is depth: fNIRS measures cortex only to a limited depth, and any comparison with fMRI has to take that into account.

Explore the poster

Click any part of the poster to open a zoomed-in, high-resolution view of that panel with a short explanation, then use Next and Previous (or your arrow keys) to step through it in reading order. Guided tour walks you through the whole thing from the top, and you can zoom, pan or go fullscreen on the full poster. On a phone, use the list of sections under the poster. Press Esc to close a panel.

Click any part of the poster to open it. In a panel, click the image to see it full size.
The full SfN 2026 poster. Each section is a clickable region.

Our poster for Neuroscience 2026 in Washington, D.C.: fNIRS-fMRI Reliability for Motor and Social Perception Paradigms: Validation of fNIRS Against fMRI. It is poster PSTR116.06, listed for Sunday, Nov. 15, 2026, 2–3 p.m.

Authors: J. Adam Noah, X. Zhang, D. Purushothaman, S. Sanchez-Alonso, V. L. Gracco, D. J. Ostry, N. Rao, M. Tiede and J. Hirsch, from the Yale School of Medicine, Yale University, the Yale Child Study Center, Haskins Laboratories and McGill University.

fNIRS (functional near-infrared spectroscopy) has a lot of promise for natural, real-world tasks in developmental and social neuroscience. But before we lean on it, we need to know how well it agrees with fMRI, and that has to be tested on more than simple reference tasks.

The aim: compare fNIRS hemodynamic (blood-flow) responses with the fMRI BOLD signal using two calibrated benchmark tasks, one motor task and one dynamic-face (social perception) task.

The same benchmark tasks were run with fNIRS (a Shimadzu LABNIRS system) and with fMRI (a Siemens MAGNETOM Prisma 3T scanner).

  • Task 1, finger-thumb tapping: left hand or right hand, a focal benchmark for primary sensorimotor cortex. Blocks of 15 s tapping and 15 s rest, 6 minutes in total, identical for fNIRS and fMRI.
  • Task 2, dynamic faces: pre-recorded videos of children’s faces smiling, moving and chewing (stimuli from Pitcher et al., 2011), aimed at the posterior superior temporal sulcus (pSTS).

The figure shows the task timing and the recording setups.

Where the fNIRS sensors sit. The scalp models show the optode layout from the front, right, left, back and top. Red dots are emitters (light sources), blue dots are detectors, and green dots are fiducial landmarks used to line the cap up on the head.

fNIRS reproduces the left/right pattern seen in fMRI. When people tapped with the left hand, activity showed up in the right primary sensorimotor cortex (labelled M1/S1), and the reverse for the right hand.

These are fNIRS results drawn on the cortical surface: left panel for left-hand tapping, right panel for right-hand tapping. Warm colors are task > rest; blue is rest > task.

The same tapping task measured with fMRI (BOLD), shown in sagittal, coronal and axial slices. The M1/S1 labels mark primary sensorimotor cortex on the side opposite the tapping hand, which is the pattern fNIRS picked up in the previous panel. Together they show robust fNIRS–fMRI agreement in hemispheric lateralization.

Both methods pick up the face network. While people watched the dynamic face videos, fNIRS (left) and fMRI (right) both detected the dynamic-face network, including multiple sites along the posterior superior temporal sulcus (pSTS). The fMRI renders show both positive and negative BOLD responses.

fNIRS reliably detected activity in visual cortex and lateral-occipital cortex, and also in the superior and middle temporal lobes and pSTS, with high spatial correspondence to the fMRI BOLD signal.

The fMRI slices show how deep that activity sits. One crosshair marks the right fusiform gyrus; the other marks the pSTS, where the crosshair is about 1 cm deep and activity in the sulcus is 2.5–3.0 cm deep. fNIRS reaches into superficial cortex, roughly half the distance between a source and a detector optode.

A note on the pictures. fMRI data are truly 3D, so they are shown in a semi-transparent glass brain with the sulci visible. Continuous-wave fNIRS is not true 3D data, so its results are drawn on the cortical surface, with depth limited by the NeuroDOT sensitivity model. Any direct fNIRS–fMRI comparison has to account for that difference.

Work in progress: how deep can fNIRS see? For a single participant, we combined that person’s own fMRI and T1 anatomical scans with a NeuroDOT fNIRS sensitivity map. Overlaying the fMRI face activation, the fNIRS sensitivity and the optode positions lets us estimate how sensitive fNIRS is to the superficial and deeper parts of two face areas, the fusiform face area (FFA) and the pSTS.

fNIRS and fMRI line up well in space for both the motor task and the face-video task.

Why that matters: in the scanner, social stimuli have to be recorded video, which removes two defining parts of real social exchange. A recorded face can’t return your eye contact (gaze reciprocity), and it can’t respond to or mirror your expressions (facial mimicry). fNIRS has neither limit, so we can study live, face-to-face interaction with real two-way gaze and facial expression. That matters most for groups where natural social exchange is central to the question.

The limitation: continuous-wave fNIRS only measures cortex to a limited depth, while fMRI is volumetric. Next, we are building methods into our pipeline to compare fNIRS and fMRI sensitivity at different depths of the pSTS during face processing.

The take-home: fNIRS and fMRI show spatial reliability across both the motor and the social perception tasks. That supports fNIRS as a platform for developmental settings where fMRI is impractical and ecological validity is essential.

The face videos come from Pitcher, Dilks, Saxe, Triantafyllou & Kanwisher (2011, NeuroImage), and the sensitivity modelling uses the NeuroDOT toolbox (Eggebrecht & Culver, 2019).

This work is supported by NIMH Grant R61 MH138705-01 to J. Hirsch. The content is solely the responsibility of the authors and does not necessarily represent the official views of the National Institutes of Health.

Download the full poster (PDF)

Come by if you’re at SfN

If you’re at Neuroscience 2026 in Washington, D.C., come find me at poster PSTR116.06 on Sunday, November 15. I’ll be at the poster from 1 p.m. (the time printed on the poster is 2–3 p.m.). Stop by and talk with me about what the lab is doing; I’d love to hear what you’re working on too.

Poster details

Title: fNIRS-fMRI Reliability for Motor and Social Perception Paradigms: Validation of fNIRS Against fMRI
Authors: J. Adam Noah, X. Zhang, D. Purushothaman, S. Sanchez-Alonso, V. L. Gracco, D. J. Ostry, N. Rao, M. Tiede, J. Hirsch
Affiliations: Yale School of Medicine; Department of Psychiatry, Yale School of Medicine; Department of Psychiatry, Yale University; Yale University; Yale Child Study Center; Haskins Laboratories; McGill University
Poster: PSTR116.06, Neuroscience 2026, Washington, D.C., Sun., Nov. 15, 2026, 2–3 p.m.

This work is supported by NIMH Grant R61 MH138705-01 to J. Hirsch. The content is solely the responsibility of the authors and does not necessarily represent the official views of the National Institutes of Health.

Schematic of the Neurospectrum pipeline in four stacked steps: signals on a graph; graph wavelets with node attention; a T-PHATE-regularized autoencoder producing a latent trajectory; curvature, path signatures, Betti curves and RNN summaries feeding a feed-forward network

Reading the Shape of Brain Activity: Our Neurospectrum Paper

I’m happy to share a new paper I co-authored, now out in Neurocomputing: “Neurospectrum: A geometric and topological deep learning framework for uncovering spatiotemporal signatures in neural activity.” First author Dhananjay Bhaskar and senior author Smita Krishnaswamy led a big team on this one, and I’m glad I got to be part of it. Below is a short plain-language summary, followed by a slide deck you can click through or download.

Schematic of the Neurospectrum pipeline in four stacked steps: signals on a graph; graph wavelets with node attention; a T-PHATE-regularized autoencoder producing a latent trajectory; curvature, path signatures, Betti curves and RNN summaries feeding a feed-forward network
Schematic based on Bhaskar et al., 2026: how Neurospectrum goes from signals on a graph to a trajectory and its shape. My own drawing, based on the paper’s description.

The problem

Brain recordings are messy. Whether it’s fMRI, calcium imaging, or the optical signals my lab works with, the data are high-dimensional, noisy, and always changing. Many of the standard tools, like PCA, ICA, and correlation-based connectivity, lean on assumptions such as linearity or stationarity, and they often average over space or time. That can wash out the fine-scale, moment-to-moment patterns we actually care about.

What we did

Neurospectrum treats brain activity as a path through time and then asks what shape that path has. It works in three steps:

  • Space. At each moment, the signals sit on a graph of brain regions, cells, or sensors. Graph wavelets pick up patterns at several spatial scales, and a learnable attention step weights the regions that matter most.
  • Time. An autoencoder, regularized with a manifold-learning method called T-PHATE, compresses each recording into a smooth, low-dimensional trajectory.
  • Shape. The trajectory is summarized by its curvature (how sharply it turns), path signatures, Betti curves from persistent homology (its topology), and a recurrent network. Those features feed a small predictor.

The pieces are modular, so you can swap summaries in or out, and when they are differentiable the whole thing can be trained end to end.

What we found

The team tested it on simulated coupled oscillators (the Kuramoto model, 100 oscillators), two-photon calcium imaging from mouse visual cortex, and resting-state fMRI collected before and after a decision-making task in 58 adults (27 with OCD, 31 healthy controls). Neurospectrum beat every baseline on every task. Recovering the oscillators’ coupling strength, its error was 0.0041 versus 0.0060 for the next-best method (ICA). Decoding the visual stimulus, accuracy was 0.60 versus 0.54. Telling OCD from control participants, accuracy was 0.70 versus 0.65.

The part I find most interesting: after the task, people’s brain trajectories bent more sharply, and that rise in curvature was larger in OCD. The group difference was statistically significant in males (p = 0.0449) but not in females (p = 0.235). The attention maps also pointed to different regions by sex, such as the posterior putamen in female participants and the superior frontal sulcus in male participants.

Why it matters

This isn’t just a better classifier. It produces features you can look at and reason about, like how much a brain state “turns” after a task, or which regions drive a difference. The paper didn’t use fNIRS, but the graph nodes can be sensor locations, and the wavelet step is designed to be robust to differences in sensor indexing and placement. That makes fNIRS optode montages a natural next test, and I’d like to try it. There are caveats: the clinical result rests on a single fMRI dataset, the method costs more compute than simpler tools, and the best summary feature depends on the task. The numbers above are from the open preprint, and the code is on GitHub.

Read the paper

Article (DOI): https://doi.org/10.1016/j.neucom.2026.135412
Open preprint (bioRxiv): https://doi.org/10.1101/2023.03.22.533807

Citation: Bhaskar D, Zhang Y, Moore J, Ketonis P, Gao F, Grossenbacher-Rieck B, Wolf G, Khasawneh FA, Munch E, Noah JA, Pushkarskaya H, Pittenger C, Greco V, Krishnaswamy S. Neurospectrum: A geometric and topological deep learning framework for uncovering spatiotemporal signatures in neural activity. Neurocomputing. 2026;710:135412. doi:10.1016/j.neucom.2026.135412

The slides

Here is my eight-slide summary of the paper. Use the arrows, your keyboard’s arrow keys, or the thumbnails, and hit Fullscreen for a bigger view.

Title slide: Neurospectrum, a geometric and topological deep learning framework for uncovering spatiotemporal signatures in neural activity, with the full citationBackground slide: neural signals are hard to read; common tools versus NeurospectrumData and approach slide: Kuramoto simulations, calcium imaging and fMRI test bedsMethod slide: graph, trajectory, shape, with a schematic of the Neurospectrum pipelineResults slide: Neurospectrum beat every baseline on every task, with four key numbersSlide: what this could mean for fNIRS, ideas to tryLimitations and next steps slide, with 58 fMRI participantsReference and links slide with the DOI, preprint and code links
1 / 8

Download the slides (PowerPoint)

Right-hemisphere brain rendering from Figure 2 of Purushothaman et al. 2026: red-yellow clusters (supramarginal gyrus, somatosensory and motor cortex face areas) show lower activity in first episode psychosis than in typically developed participants; blue clusters (angular gyrus, somatosensory association cortex, dorsolateral prefrontal cortex) show higher activity.

Looking at a Live Face: What We Learned About Early Psychosis

Our new paper is out in Frontiers in Neuroimaging, led by Deepa Purushothaman with Xian Zhang, Rahul Singh, Cenk Tek, Vinod Srihari, Joy Hirsch and me. It asks a simple question with a complicated answer: what is different in the brain when someone early in the course of psychosis looks at another person’s face, live, in the same room? The article is open access: read it here (doi:10.3389/fnimg.2026.1931240).

The problem

Difficulties with social interaction are common in schizophrenia, and they matter a great deal for how people do in daily life. Yet most of what we know about the social brain in schizophrenia comes from people looking at photos or video clips, usually alone, lying in a scanner. Real conversations aren’t like that. They are face to face, reciprocal and unscripted, and our earlier work suggests the brain handles a live face differently from a face on a screen.

What we did

We used a two-person face gaze task that our lab has used before. A lab partner sat across a table from each participant, separated by a “smart glass” window that could switch from opaque to clear. The partner watched short, emotionally evocative video clips (cute animals, or things like spiders and decay) and then looked at the participant, so the participant saw a real person’s natural, unrehearsed expressions.

While this happened we recorded several things at once: fNIRS (134 channels) and EEG (32 electrodes) from a single cap, eye tracking, and video of facial movements analyzed with OpenFace. We compared 24 people with first episode psychosis (early schizophrenia spectrum disorders), recruited through Yale’s STEP clinic, with 32 typically developed participants.

Right-hemisphere brain rendering from Figure 2: red-yellow clusters (supramarginal gyrus, somatosensory and motor cortex face areas) show lower activity in first episode psychosis than in typically developed participants; blue clusters (angular gyrus, somatosensory association cortex, dorsolateral prefrontal cortex) show higher activity.
Brain regions where activity during live face gaze differed between groups. Red-yellow: lower in first episode psychosis; blue: higher. Figure from Purushothaman et al., 2026, Frontiers in Neuroimaging, CC BY 4.0.

What we found

Activity in a set of right-hemisphere regions differed between the groups. The right supramarginal gyrus, a region we have repeatedly linked to live face gaze, along with the face areas of the right somatosensory and motor cortex, was less active in the first episode psychosis group. The right angular gyrus, superior parietal lobule and dorsolateral prefrontal cortex were more active.

In exploratory analyses, lower activity in the right supramarginal gyrus and DLPFC went with higher expressive deficit scores (blunted affect, poor rapport, less spontaneous conversation and slowed movement), and activity in the superior parietal region went with passive social withdrawal.

Behavior and EEG told a consistent story. Participants with first episode psychosis showed less spontaneous facial mimicry of their partner, shorter fixations on the partner’s face and more frequent saccades. In the first 100 to 300 milliseconds after the window cleared, their EEG responses were smaller over right temporoparietal electrodes and delayed over temporoparietal electrodes on both sides, and theta power was reduced. So the “where” from fNIRS and the “when” from EEG pointed to the same right temporoparietal area.

Why it matters, and what it doesn’t show

This is a step toward measuring social brain function in a setting that looks more like everyday life, at a stage of illness when people may benefit most from new kinds of support. The regions we found could become targets for future studies that test cause and effect, for example with non-invasive neuromodulation.

It is also important to be clear about the limits. The study is cross-sectional, so these links are correlational. There was no non-social control condition, the groups differed in sex ratio, most participants with psychosis were taking medication, and fNIRS can’t see deeper brain structures. We hope this work helps build better tools, not labels. I’m grateful to everyone who took part.

The slides

Here is a short slide summary of the paper. Use the arrows, your keyboard, or the thumbnails to move through it.

Slide 1: Title and citationSlide 2: Background and questionSlide 3: ParticipantsSlide 4: The live face gaze taskSlide 5: Multimodal recordingSlide 6: AnalysisSlide 7: fNIRS resultsSlide 8: Behavior and EEG resultsSlide 9: Interpretation and limitationsSlide 10: Reference and links
1 / 10

Download the slides (PowerPoint)

Read the paper

Purushothaman D, Noah JA, Zhang X, Singh R, Tek C, Srihari VH, Hirsch J. A multimodal approach to identify atypical face processing in first episode psychosis (early schizophrenia spectrum disorders). Frontiers in Neuroimaging. 2026;5:1931240. doi: 10.3389/fnimg.2026.1931240

The article is open access under a CC BY 4.0 license. The data are available through Dryad: doi:10.5061/dryad.gxd2547xn.

MLS NEXT U13 New England Standings – Nov 9, 2026

MLS NEXT Academy Division, U13 New England conference, standings as of Monday, November 9, 2026. A win is 3 points and a draw is 1 point. Teams are ranked by points per game (PPG), since they have played different numbers of games.

Weekend results now fully posted for Nov 7–8 include Vale Rush United 1–0 New York Elite Alleycats FC (home), FC Greater Boston Bolts 7–1 Valeo Futbol Club, and NEFC South 0–8 IFA West. Vale Rush United is 3-0-3 with 9 points, 9th in the conference on PPG.

# Team GP W L D GF GA GD Pts PPG
1 FC Greater Boston Bolts 8 7 0 1 31 5 +26 22 2.75
2 NEFC 8 7 0 1 31 9 +22 22 2.75
3 Ginga FC 6 4 1 1 22 15 +7 13 2.17
4 New England Surf SC 7 4 1 2 24 9 +15 14 2.00
5 New England Force 7 4 1 2 24 14 +10 14 2.00
6 IFA West 6 4 2 0 29 10 +19 12 2.00
7 New York Elite Alleycats FC 7 4 2 1 19 5 +14 13 1.86
8 Syracuse Development Academy 8 4 4 0 15 12 +3 12 1.50
9 Vale Rush United 6 3 3 0 20 12 +8 9 1.50
10 Bayside FC 8 3 3 2 18 18 0 11 1.38
11 New York Rush 8 3 4 1 18 27 -9 10 1.25
12 Seacoast United Mass 7 2 3 2 20 20 0 8 1.14
13 Intercontinental Football Academy of New England 8 2 3 3 16 13 +3 9 1.12
14 FC Greater Boston Bolts Metro North 8 3 5 0 16 26 -10 9 1.12
15 Seacoast United Bedford 8 2 4 2 8 12 -4 8 1.00
16 FC North 7 2 5 0 12 20 -8 6 0.86
17 NEFC South 7 1 6 0 10 47 -37 3 0.43
18 Rhode Island Surf SC 8 0 6 2 9 31 -22 2 0.25
19 Valeo Futbol Club 6 0 6 0 6 43 -37 0 0.00

Source: league match scores, league games only. Games without a posted score are not counted. Nov 8 scores that were still pending when this draft was first written are now included.

Screenshot of the NVIDIA app offering GeForce Game Ready Driver 621.14 with 'No driver installed' behind an 'Installation can't continue' dialog that says the driver is not compatible with this version of Windows and could not find compatible graphics hardware.

NVIDIA, You Had One Job: Install the Driver

Originally published on snarky.tech.

Installing a graphics driver should be the most boring thing a computer does. The app sees the video card, sees the version of Windows, downloads the matching driver, installs it, and tells you it worked. That’s it. That’s the whole job.

The NVIDIA app has turned this into a recurring adventure. For me, it fails regularly, and when it isn’t failing, it’s often showing me a status screen that doesn’t match what’s actually going on. This week’s episode is my favorite so far.

Screenshot of the NVIDIA app Drivers page showing 'No driver installed' and an offer to install GeForce Game Ready Driver 621.14, released Wed Nov 4, 2026, covered by a dialog reading 'Installation can't continue' with two details: 'This NVIDIA graphics driver is not compatible with this version of Windows' and 'This graphics driver could not find compatible graphics hardware.'
The NVIDIA app recommends a driver, offers an Install button, and then explains why that driver won’t install. My screenshot, unedited.

The app picked this driver. Then rejected it.

Look at the screen. Up top, the NVIDIA app announces “New – GeForce Game Ready Driver,” version 621.14, released Wednesday, November 4, 2026. There’s a big green INSTALL button. Behind it, a cheerful banner about new games and DLSS 5. This is the app’s own recommendation. Nobody went to a sketchy website. I clicked the button NVIDIA put in front of me.

And then: “Installation can’t continue.” Details: “This NVIDIA graphics driver is not compatible with this version of Windows.” And, as a bonus: “This graphics driver could not find compatible graphics hardware.”

So which is it? Wrong Windows? No hardware? Both? If the app can’t find NVIDIA hardware, why is the NVIDIA app offering me an NVIDIA driver for it? If my Windows isn’t supported, why did the app recommend this driver for my Windows? The app had all the information before it lit up that button. It just didn’t check until after I believed it.

“No driver installed.” Sure.

Then there’s the line in the top left: “No driver installed.” Maybe that’s true at that moment. Maybe it’s another one of those status screens I’ve learned not to trust. I genuinely can’t tell from the app, and that’s the problem. A driver tool has one dashboard that matters, the one that says what’s installed and whether the last install worked. If I can’t trust that screen, I can’t trust anything else the app tells me.

I’m not claiming to know what’s wrong under the hood. I’m saying the app doesn’t seem to know either, and it’s the one whose job it is to know.

What this should look like

  • Check first, recommend second. Detect the card and the Windows version before offering a package. Don’t put an Install button on something you’re about to refuse.
  • Tell the truth about status. Installed, not installed, failed, or rolled back. Pick the one that’s actually true.
  • Give one error I can act on. Not two that contradict each other. Tell me what you detected, what you expected, and what to do next.

None of this is cutting-edge. NVIDIA can ship neural rendering and AI-generated frames, and it’s advertising both on the same screen that can’t figure out whether my computer has a graphics card. Installing a driver isn’t a feature. It’s the floor.

NVIDIA, you had one job. Please do it before the next Game Ready Driver is ready for a game I can’t play.

A phone with a digital wallet showing an empty ID slot next to a sample Connecticut driver's license, an NFC tap reader, and a QR code stand

Connecticut Promised Me Apple Wallet in 2021. I Got Another App.

Originally published on snarky.tech.

A phone with a digital wallet showing an empty ID slot next to a sample Connecticut driver's license, an NFC tap reader, and a QR code stand
The wallet has a spot for my ID. Connecticut has an app instead. (Illustration, sample ID.)

Good news, Connecticut: after years of waiting, we’re finally getting a digital driver’s license. The DMV says Connecticut Mobile ID launches November 18. (ct dmv)

Bad news: it’s not in Apple Wallet. It’s not in Google Wallet or Samsung Wallet either. It’s another app. A separate, free “Connecticut Mobile ID” app you download from the App Store or Google Play, built by a vendor called IDEMIA. (idemia)

That’s not what we were promised.

Remember 2021?

On September 1, 2021, Apple announced the first states signed up to put driver’s licenses in Apple Wallet: Arizona, Connecticut, Georgia, Iowa, Kentucky, Maryland, Oklahoma, and Utah. Governor Lamont was right there in the press release: “We’re pleased to be one of the first states working with Apple to deploy driver’s licenses and state identification cards in Apple Wallet.” (apple)

One of the first. Let’s check the scoreboard. Arizona, Georgia, Iowa, Maryland, and Oklahoma from that original list all have IDs in Apple Wallet today. Apple’s list is now up to 16 states plus Puerto Rico. Connecticut isn’t on it. (apple, macrumors)

When I originally complained about the slow rollout last year, my question was simple: why is this taking so long? More than a year later, the answer appears to be “we were building something else.”

Wallet support is “coming soon.” Sure.

The IDEMIA help page literally asks the question: can I put my Connecticut license in Apple, Samsung, or Google Wallet? The answer: “These features will be coming soon.” (idemia)

How soon? In May, the State Bond Commission approved money for a “State of Connecticut digital wallet,” with a goal of rolling it out “by the end of the summer.” The same plan pushes compatibility with Apple, Google, Samsung, and other commercial wallets out to August 2027. (ct governor) Summer came and went. The app now lands just before Thanksgiving. And the thing the governor bragged about in 2021 is officially the sequel.

Why the app is the wrong call

The whole point of Apple Wallet is that it’s already on my phone. My credit cards, boarding passes, and transit cards are there. With an ID in Wallet, you tap your iPhone or Apple Watch on the reader, approve with Face ID, and you never unlock or hand over your phone. (apple)

Here’s what Connecticut is offering instead: download an app, wait for a verification text, photograph the front and back of your license, do a selfie dance, and then show your ID by generating a QR code for a “verify reader” to scan. (idemia) Businesses aren’t required to accept it, they need a “compatible verification app” if they do, and the DMV itself says acceptance “will initially be limited.” Police won’t take it, and you can’t use it to vote. Keep carrying the plastic card. (ct dmv)

And now the confusion part. If you have a passport, Apple Wallet already lets you make a passport-based Digital ID that TSA accepts. (tsa) So a Connecticut resident heading to Bradley could have a Digital ID in Wallet, a separate state app, and the physical license they still have to carry. Three IDs, one person, and a TSA officer wondering which one you’re about to wave at them. Then, maybe in 2027, a fourth version in Wallet.

It’s not like the neighbors are setting the pace either. TSA lists New York’s mobile ID as the “NY MiD app” only, and no New England state is on Apple’s list. (tsa, apple) Connecticut had a real shot to be the first in the region to do this the easy way. Apple put its name next to ours five years ago.

Here’s how this ends. Calling it now.

The DMV commissioner says he’s looking forward to “the increased adoption and use of Mobile ID amongst residents.” (ct dmv) Here’s my prediction for how that goes.

  • Step 1: Launch a standalone app nobody has heard of, that most businesses don’t scan, that police won’t accept.
  • Step 2: Few people download it, because why would they? Their phone already has a wallet, and they still need the card.
  • Step 3: Businesses see few customers using it, so they don’t bother setting up a verifier. Which means even fewer people use it.
  • Step 4: Somewhere around the August 2027 deadline, someone in Hartford points at the download numbers and says there “isn’t enough interest” to justify the Apple Wallet work.

Low adoption won’t mean people don’t want a digital ID. It’ll mean the state shipped the version people didn’t want, then used the results as proof. I hope I’m wrong. I’ve been wrong before. Not often about the DMV.

What Connecticut should do

  • Make Apple, Google, and Samsung Wallet the priority, not the sequel. Sixteen states figured it out. Several of them were in the same 2021 press release as us.
  • Don’t judge demand by the app. If you want to know whether people want a digital ID, measure it after it’s in the wallet they already use.
  • Give us an actual date. “Coming soon” has been the plan since 2021.

So I’ll ask again, five years in: why is this taking so long? And when it finally shows up in Wallet, will anyone in Hartford still be paying attention?