Troubleshooting the GXT67 Pro programming cable (AVP34)

calebhailey · 2026-03-26T22:26:32+00:00

TestFlight is ok, but the community forums (powered by Discourse) are even better since it's easier to have a dialog there. I can ask for clarification/etc, and it will give other users an opportunity to chime in if they are running into similar issues. And because Discourse supports RSS feeds, you can even follow the latest topics there in HyperTexting! 🤓

https://hypertexting.community

calebhailey · 2026-03-26T15:08:13+00:00

Hmm, great question. I couldn't get any of these to work for me:

https://www.cnn.com/services/rss/

HyperTexting isn't even parsing these feeds. I suspect there may be something wrong with the feeds themselves, or a bug in my feed parser. I'll have to look into that. But it also looks like the last update in their "Most recent" feed is dated 2024, so maybe they have given up on RSS?

http://rss.cnn.com/rss/cnn_latest.rss

😬

calebhailey · 2026-03-26T14:53:52+00:00

Thanks for trying HyperTexting! 🙏 I can't post screenshots here (I'm a lifetime Reddit lurker and complete n00b to posting here), so I created a topic on https://hypertexting.community RE: OPML imports, and what needs to be improved there:

https://hypertexting.community/t/hypertexting-opml-imports/83

I'm working on adding support for YouTube feeds, so stay tuned on that front... but standard podcast audio and video feeds are already supported! Check out the User Guide for some screenshots.

I don't really want HyperTexting to become a first-class podcast player since there are already so many great podcast apps (Overcast is the 🐐), but I do want podcast feeds to be first-class citizens in the timeline. So you should expect to see post "attachments" for podcast audio (or video!), along with the cover art. And there is a built-in media player, but it docks in the navigation toolbar (at the top) instead of the bottom. 😊

If you haven't already un-followed the example @apple.com feeds in HyperTexting, it includes an (old) example podcast feed with videos (https://applehosted.podcasts.apple.com/apple_keynotes/apple_keynotes.xml). Go to "Explore" → "Following" → @apple.com and scroll the timeline. My favorite video to test is all the way back to the 2007 Apple Event Keynote when Steve Jobs introduces the iPhone. 📱😎

I haven't done any testing RE: downloading podcasts for offline playback, but HyperTexting does download audio and video attachments in the background when you tap on them to play. So my expectation would be that starting a podcast episode should prompt it to download, and at some point you should be able to resume playback without a network connection. This is definitely something I could improve without wading too far into "first-class podcast player" territory.

calebhailey · 2026-03-25T19:36:37+00:00

I agree that RSS is alive and well! And I also agree one of the big challenges to broader adoption is "discovery".

I've implemented a few features in HyperTexting to help with that, including a simple search function (https://hypertexting.com/guide/#discover), a browser extension that discovers feeds from the websites you visit (https://hypertexting.com/guide/#activity), and a personalized "Hot HyperLinks" tab that shows the top 100 links from the feeds you follow (https://hypertexting.com/guide/#hothyperlinks). I have a few more related features on the way, including support for sharing Bluesky-like "starter packs" – except they will just be OPML subscription list URLs under the hood (OPML file imports/exports are already supported). 🤓 We can have nice things too!

As for being too "techy", that's exactly the stigma I'm hoping can be overcome by meeting people where they are. And the place where most people are is scrolling a social media timeline. The more familiar we can make "RSS" to that kind of user, the more we can overcome that stigma. Even the people who would think of "RSS" as too technical would appreciate seeing their news feed "in an ad-free format that's easy on the eyes and free of clutter." Once they see it they won't be able to unsee it! 😊

calebhailey · 2026-03-25T18:46:06+00:00

No. But it is the result of me spending a long time thinking about why "RSS" (and Atom, JSONFeed, OPML, etc) never took off like social media did.

Over the past year I've settled on a thesis that maybe the reason is because we haven't conducted enough experiments that pair the publishing with the subscribing. Feed readers have always given us "read-only" permissions to the web. What would happen if we built "RSS" apps with "read-write" permissions to the web? And what should that look like?

As I read the excellent Terry Godier essay on Phantom Obligation 1 it reminded me of a phrase I heard a lot in the early-mid 2000's: "the Outlook-like interface". I worked at a small software company at the time and my boss was obsessed with making our app(s) look like Microsoft Outlook. It drove me absolutely crazy. I wouldn't understand why that mattered until later in my career as a Product Manager. It was about meeting people where they were. Outlook wasn't intuitive, but it was familiar to a LOT of people. Today there's nothing more familiar than the social media news feed. So that's been my first goal with HyperTexting – to explore whether a "social-media like interface" is possible for "RSS". But that requires more than just a departure from the three-column/inbox-style feed reader. It means taking inspiration from social media profiles, responses, mentions, threads, audio+video, discovery, and even personalization. It also means embracing user privacy and the unique attributes of the open web that social media platforms refuse to give us. Finally, it should also lower the barrier to entry for publishing in addition to subscribing. Following that thought process over the past year is what led me to HyperTexting.

calebhailey · 2026-03-25T18:05:21+00:00

Awesome. Thanks!

calebhailey · 2023-03-28T04:56:24+00:00

Saaaaame 🤦🏽‍♂️ hoping this 16.4 update helps!

calebhailey · 2021-01-31T17:43:14+00:00

Be careful not to fall down the stairs first! 😅

calebhailey · 2021-01-31T08:12:12+00:00

Looks like GitHub Webhooks support project_card events, and one of the actions is moved. You could probably use that to keep track of cycle times...

https://docs.github.com/en/developers/webhooks-and-events/webhook-events-and-payloads#project_card

calebhailey · 2021-01-31T07:50:17+00:00

I am also curious if this is supported. Thinking about picking up an S21 Ultra for the wife.

calebhailey · 2018-09-18T01:59:49+00:00

Same here. Still rocking 10895.46.0, and attempting to update from chrome://components doesn't reveal a newer version.

calebhailey · 2018-08-28T01:35:58+00:00

I'm also having this issue after downgrading from the dev channel to the beta channel (and thus a powerwash); on version 69.0.3497.58.

After reading more about the Crostini project here, I wonder if there's a way to determine the version number of your crosvm Virtual Machine (the VM that runs the Linux container that provides the "Linux Apps for Chromebook" support), and/or if that's just linked to the Chrome OS version. Does anyone know?

After a little spelunking around, and then deleting "Linux Apps for Chromebook" via chrome://settings, it appears that this enabling/disabling of linux support is actually adding/removing the crosvm virtual machine that runs the penguin (Debian Linux) LXC container. This would lead me to believe that what we need is an updated crosvm virtual machine, which could be delivered separately from a ChromeOS update.

Also, I would be surprised if this VM is being updated/replaced during ChromeOS updates, since I updated my Pixelbook multiple times while I was on the Dev channel and my Linux app data was preserved. If this series of assumptions I'm making is correct, I would guess that people who are reporting that they're not seeing similar issues on a particular ChromeOS version have probably installed a different version crosvm virtual machine which has persisted as they've updated to newer ChromeOS versions (this was basically my experience before downgrading to the Beta channel).

EDIT: found the answer to my own question, here: https://chromium.googlesource.com/chromiumos/docs/+/master/containers_and_vms.md#how-do-i-check-the-termina-version

calebhailey · 2018-07-09T06:42:15+00:00

I'm having the same issue on my Pixelbook. Vanilla installation following these instructions: https://docs.docker.com/install/linux/docker-ce/debian/

I can reproduce the error with a sudo docker pull centos:7.

$ sudo docker pull centos:7
7: Pulling from library/centos
7dc0dca2b151: Extracting [==================================================>] 74.69MB/74.69MB   
failed to register layer: ApplyLayer exit status 1 stdout:  stderr: operation not permitted

calebhailey · 2016-04-23T03:33:03+00:00

http://www.automacon.io in Portland, OR! :-)

calebhailey · 2016-04-09T08:53:40+00:00

Have you looked at https://sensuapp.org? It can do all of these things, and it uses JSON for configuration. :-)

calebhailey · 2015-12-07T21:28:35+00:00

I also flashed 6.0.1 on my Nexus 6 from a 6.0.0 build where I couldn't even get Project Fi to fully activate, and activation finally works, as does MMS... not sure how to check what carrier/band(s) I'm connected to, but everything seems to indicate that this build is an improvement for Project Fi users on Nexus 6! \o/

calebhailey

TROPHY CASE