Tech
Fitbit On Pixel Watch Broken
The March 5, 2026 Wear OS update that Google released has broken the Fitbit app. The Fitbit app of my Pixel Watch 3 is significantly over counting/doubling my steps, mileage, and calories consumed. It looks like it is doubling the counts. As an example, I have taken two walks today and the workout details appear correct, one 12 minute, 0.69 mile walk of 1,515 steps and a second 24 minute, 1.35 mile, 2,967 steps walk, but the overview shown on my phone and watch shows a total of 9,827 steps and 4.7 miles.
As an experiment, I shut off my phone and watch then started my watch. After first start up the watch shows the correct step count, but eventually it connects to the Fitbit servers and is then updated with the higher step count.
I am seeing a recommendation on Reddit of a fix involving resetting the watch, which I think means that I will have to re-install apps, but before doing that I decided to try disconnecting the watch from the Fitbit app on the phone.
After I did the disconnect I deleted the day’s step and distance data from the Fitbit app and the backend server so that it displayed 0 steps. I then restarted my watch, observed that it displayed the correct step count, and then reconnected the watch to the Fitbit app, and after a short period of time the watch and the app on the phone showed 5,462 steps.
Next, I went for another walk of 2,662 steps and afterword it showed the correct sum of about 8,124 steps. I am not ready to declare the situation is fixed with my watch but it’s looking positive.
Boox has released second generation of their 10.3-inch Go series e-Ink tablets that appear intended to compete with the Remarkable 2. There are two versions of this generation, a $400 without a front light and a $450 model with a front light. A major negative, in my opinion, is that Boox has replaced the Wacom EMR stylus support with their InkSense capacitive stylus is that is less accurate and requires charging. I would not buy this tablet due to this choice by Boox.
I would wish that Boox would release an 8-inch e-Ink tablet with Wacom EMR support but that appears to be less likely to happen as time passes.
I am watching a video overview of Inkwell, which is Manton’s RSS app released last week. I’ve tried using Inkwell but find it doesn’t fit in to my web reading triage workflow. I send everything to Readwise Reader where I do all my reading, so the blogging and quote blogging of Inkwell would be more useful for me in Readwise. One thing that I am intrigued by is the Reading Recap feature in Fading, but I don’t know whether I would really use that feature a lot or not.
Computer Industry Pricing
How I Use RSS
As I have observed earlier, right now there is a lot of good energy around RSS with new feed readers popping up nearly every week. Yesterday Manton Reece released is take on an RSS app called Inkwell that is a companion to his micro.blog service/app that I use to host this blog. Because Inkwell integrates with the blogging platform that I use, I find there are reasons to consider using it while I have resisted looking at other apps.
I have been using RSS since I first learned about it in the early 2000s. Like many, I used Google Reader mostly because it was a web app that I could use on any device. Over the years I tried desktop and phone apps like NetNewsWire, but in the end found myself back to the simple web apps that Dave Winer wrote over the years.
The 2026 iPad Air M4: Early Impressions:
The second change is memory. The M4 brings 12GB of unified memory, up from 8GB on the M3 model. More RAM means better multitasking and more headroom for demanding tasks. Transcription in Voice Memos and background removal in Pixelmator happen almost instantly. I feel it in Lightroom as well.
My primary concern about the MacBook Neo is that I don’t think the 8 GB of RAM is enough in the current AI era of personal computing. While the quote above is about the new iPad Air, I think the point about the benefit of moving from 8 GB to 12 GB is apt.
Later in his post Om also ponders whether the Neo is a better value than the Air given it includes a keyboard. I do wonder whether Neo will affect iPad sales.
More Experimentation With Android Desktop
I have paired the Nillkin folding Bluetooth keyboard to my Pixel 10, connected the phone to the BenQ monitor and enabled Android Desktop mode, thus providing me a desktop computing device. The keyboard has a built in trackpad to enable me to move the mouse on the desktop and I have figured out how to run multiple (virtual) desktops at the same time. I have ordered a portable, 15-inch monitor that I have been meaning to buy for some time as a backup display and to experiment further with this idea of really portable computing. For blogging, I am writing this in Obsidian running on the phone and I will post this item to the blog later from my MacBook.
I think the whole idea of the MacBook Neo comes down to one question, is $599 a low price?
It occurs to me, that the MacBook Neo is essentially the often desired iPad that runs MacOS.
What Is Low Cost?
My Thoughts About Android Desktop
I watched XDA’s presentation of the Android desktop mode available in the Android 17 beta. Desktop mode is available with Android 16 too and I’ve tried it out and it’s not bad. I’ve long been intrigued by the idea of using a smartphone as my only computing device, and I honestly think this is best applied to foldables.
As I see it, the main impediment to such an all-in-one device is the lack of wireless connectivity to monitors, keyboards and mice. Imagine being able to use the desktop mode of your phone while the phone is still in your pocket.
It does appear that while desktop mode is available with all Android devices, it’s primary purpose is as a replacement to Chrome OS. For Google, Android desktop mode is a consolidation of operating systems. Google seems convinced that it’s worth it for them to offer a desktop computing user interface for their operating system, even though Chrome OS only has a small percentage of the desktop market, per Wikipedia.
I am not convinced that Android Desktop offers anything for the desktop market, and rumors are Apple may be soon announcing a low cost Macbook built on their A-series processors that will be hard to compete against.
The one scenario I can think of that might be interesting is Google pitching the idea of the Pixel Fold being the computing device that is all one will need, and therefore try to justify the greater than $1,000 price tag for the Fold. The math works when compared to the sum cost of a phone, tablet and desktop if the device fits all these use cases. However, I think for this to work there must be wireless connectivity to keyboard, video, and mouse or at the very least an easy to use drop-in docking station.
Two Way RSS
Yesterday I wrote a draft post about RSS Feeds and I wrote this:
A lot of pixels are being dedicated to writing about Really Simple Syndication (RSS) feeds, which I think of as a “broadcast medium” for text and files.
The cycle of yearly new phones from Apple and Google are not about significant changes between one year to the next. I don’t think Google expects Pixel 9a users to want to replace the phone they bought last year with the Pixel 10a this year, therefore it makes sense that the Pixel 10a has incremental improvements. I really don’t know why the reviews of these phones focus on the small number of changes from one phone to the next. It makes more sense, in my opinion, to compare the upcoming Pixel 10a to the Pixel 8a and 7a. My guess is that the improvements from the 7am, or older, is the most compelling reason to by a Pixel 10a.
In this video on YouTube, Kitt Betts-Masters shows the technology behind Wacom’s EMR pens. I currently primarily use felt nibs in the EMR pens I use with my Viwoods AI Paper Mini and Boox Note Air 3C, but I am curious about how the ceramic nibs feel. My concern has been with the effect of using ceramic nibs, even the ones provided by Viwoods, on the life of the screen.
I spent the afternoon working on and testing Scott Hanson’s dockerized version of Feedland. I’ve written notes but I don’t have the time now to edit and post them, which I will do this weekend. The net is that like the other time I installed Feedland in my home lab, I could not get browser access via HTTP to work. The web browser just simply refuses to load the site and displays an SSL error message. The good news is that I did get access to work via my Nginx and duckdns.org configuration in the same manner as I have done with other apps hosted in my home network.
I have moved some equipment around in the home office so that I can use the adjustable/standing desk while standing. This is the first time I have experienced moving my Macbook between external monitor configurations and I am impressed by the fact that it remembers the different configurations.
Down The Drummer Rabbit Hole
Earlier today I noted that Dave had posted about the issue I encountered on January 30 preventing me from publishing my Daynotes using the “default” blogging tool in Drummer referred to as “Old School,” which is descriptive of a day based blogging format.
I started the process of making and testing the changes that Dave suggested, finding them to be more involved, but the net result is that the Daynotes site is now served by HTTPS rather than only being accessible via HTTP.
When the ability to build the blog from within Drummer broke I did my own work around by creating a new OPML file that is served by my instance of PagePark, which is Dave’s web server app that knows how to render OPML files for web browsers. For now I am going to continue using my “new” Daynotes outline file while using the Drummer blog for longer articles. My simple forwarding url for daynotes (daynotes.frankm.info) will go to single outline page while I have created a new forwarder for the Old School site (oldschool.frankm.info).
Appears that Dave is now aware of the problem with the Old School blogs. He says the real issue is that the blogs are now served by https and the template they are based on does not support that. He provides instruction for how to fix, which starts by downloading a minimal template, editing it, putting the template html file on a public server, and then adding a header variable to the blog outline. Unfortunately at the moment Github is down so I cannot work on the fix, which for me will involve hosting the template file on my shared files host that is built from a Github repo. More details are in my Daynotes outline.
Analyze Oil Consumption Using NotebookLM
Of all the AI tools currently available I use Google’s NotebookLM the most. My best way to describe NotebookLM is that one can use it to apply Google’s Large Language Models toward a topic based on sources for information that one provides. For example, when we were researching health insurance plans last fall I created a notebook in NotebookLM and uploaded to it as sources PDFs provided by the insurance providers. I then used the chat in the notebook to ask questions about the different plans, which I then saved for future reference.
I have a 2013 GMC Terrain and a few years past I learned that this make and model SUV has a history of burning oil, so I have been diligently checking the oil level once a week and after long drives during trips. I log the date, odometer reading, and oil level in a note in Google Keep using my phone and I wish Gemini were integrated in Keep so that I could directly ask questions like how many miles have been driven and when is the last time I added oil.
Google has not added Keep as a source for NotebookLM, which I think would be logical, but what I can do is send (export) a note in Keep to a Google Doc which I can then add as source for NotebookLM. Today I exported each of my three log notes to a Google Doc, created a notebook in NotebookLM and add these docs as sources. NotebookLM correctly identified the sources as a maintenance log for a vehicle but it didn’t know which type of vehicle nor did it know the year the entries started because I only recorded the month and date. I created a README note that I added as a source in which I specified that the first date was in 2024 and that the logs are for a 2013 GMC Terrain. I also added some information about the dipstick markings.
With the oil logs in NotebookLM I am able to ask simple questions like, how many miles were driven between the last oil check and the prior check? I asked NotebookLM how many miles were driven in 2025, and it then offered to make an infographic that broke down the 2025 mileage by month. NotebookLM also created a detailed vehicle usage and oil consumption analysis report.
NotebookLM provides me with a simple and powerful way to analyze this data, but the fact that Google Keep cannot be a source means that as I update the current log note I will have to re-export it to the Google Doc and refresh that doc source in NotebookLM. I hope that in the future Google will add Keep as a source to either Gemini on my phone or to NotebookLM.
Expectations For The Pixel 10
I got the Pixel 10 for Christmas. We ordered it from Best Buy during their “Black Friday” sale at a cost of $549, when launched this phone cost $799. With an $80 trade-in of a Pixel 6a the total cost to me is $469, which is a very good price for a “flagship” phone.
Before I received the Pixel 10 I wrote this expecting it to be a blog post but I never published it, so now I am going back and I am going to put in quote format my original expectation and then my current point of view after one month of use.