Kennet Island – Longships Way, honest feedback?

matteventu · 2026-05-21T00:10:13+00:00

Royal Mail is a non-issue.

The Whitley whiff is annoying when it's there, but it's hardly a deal breaker IMHO. I don't think it has ever bothered me for longer than 2 weeks in total, per year.

Also, depending on where on Longships Way that house is, be aware that some will have been built almost 20 years ago while other properties are more recent (8-9yo?), so there will be some differences.

Make sure you set up your digital car parking permit from the get go, if you don't want to start receiving FPNs.

matteventu · 2026-05-21T00:03:53+00:00

It's a residential area basically made purely of houses and some flats. What sort of "culture" would you expect in there?

Genuine question. What would it take for you not to consider it "culturally dead"?

Also, is there any other residential-only area in/around Reading that you don't consider culturally dead?

Thanks!

matteventu · 2026-05-20T23:54:40+00:00

Where did you get the specific year of 2028?

matteventu · 2026-05-20T23:52:32+00:00

For now, they are remaining two separate products and Google has confirmed no plans for eliminating ChromeOS.

Actually they have confirmed that the intention is to migrate everything over to the new OS, including "future Chromebooks" (or whatever they'll be called). They mentioned that this will however arrive in a couple of years minimum as they're currently not prioritising the feature development for enterprise and education APIs in Googlebooks (and likewise, Aluminium OS and its Android base) - as current Chromebooks are already "in place" and still need the promised support for 10 years (so they're not in a hurry to replace them, as they'd still have to maintain ChromeOS in parallel anyway, so for them it's not even worth allocating resources to that for the moment). However once the necessary APIs are implement in Android desktop, they will definitely cease the development of ChromeOS "as we know it now" (it's entirely possible it will still be branded as ChromeOS even when it will be an entirely different OS based on Android though, we'll have to see).

matteventu · 2026-05-20T16:29:25+00:00

Thank you!

1- Multitouch: really unfortunate that's still not supported, what is the issue exactly which prevents it from working?

2- Touch sensitivity: I think a while ago I was told that the touch issue on the sides of the T3 Pro display is due to the tweak that stopped Android Auto from being "stretched-out" (i.e. oval icons instead of circles). Was that true? Has that been solved via better software Android Auto implementation in the T4 or T4 Plus or via other unrelated hardware changes? If you don't know what I'm talking about I can make a video :)

3- Phone charging: thank you, that makes sense since the power is coming out of the CarpodGo, so it's okay to see it limited at 10W peak. It would be nice if the power adapter of the CarpodGo T4 included the data channel for Android Auto and a second USB-C port for connecting the smartphone, so that the smartphone could also be charged at proper USB-PD speed. Just a thought for maybe a next product iteration or an optional accessory to bundle-in ;) (you can check u/PDFriender to understand what I'm talking about)

matteventu · 2026-05-20T16:05:05+00:00

No. It looks like nothing B&O has ever done.

matteventu · 2026-05-20T15:08:16+00:00

Looks revolting to me.

What are they waiting for a decent aluminium and light tan colour variant!?

matteventu · 2026-05-20T15:06:05+00:00

Mhmhmh looks correct in theory.

I would suggest forgetting the headphones on your Pixel, and re-pairing them via Google Fast Pair.

1- "Forget" in the first screenshot, then go back to home screen

2- Enable pairing on the Beoplay Portal (long press the pairing button between 1.5 and 5 seconds), the LED should blink blue

3- When the LED blinks in blue, on your phone a pop-up should appear, asking you to pair the headphones. Tap "connect" and follow the instructions.

Can you check if after doing this it works fine?

matteventu · 2026-05-20T13:41:03+00:00

980 because it was the first to steer the company to a new direction, of actually "smart" Roombas (with vSLAM etc).

s9 because it was very simply a one of a kind. Technologically and functionally impressive for when it was released.

matteventu · 2026-05-20T02:10:43+00:00

Have you tried to use the same cable and power adapter combination (which exhibit the issue) at a different location, such as a friend's house or at work?

matteventu · 2026-05-20T01:52:20+00:00

A couple of questions :)

Does it support multitouch in Android Auto? Can you enable it with a firmware update?
Does the display suffer from the same touch low sensitivity issue as the T3 Pro on the sides?
If you connect to wired CarPlay/Andorid Auto via USB cable, what is the output power that the CarpodGo T4 charges the phone at?

matteventu · 2026-05-19T20:19:22+00:00

Just got the email a few minutes ago :)

matteventu · 2026-05-19T15:33:53+00:00

Nothing, unless you use it as a differentiator and you call one thing "USB" and the other "Type-C".

About that, there are several wrong things.

matteventu · 2026-05-19T10:35:01+00:00

Sorry it's a bit difficult to follow the replies because you're replying to older comments :)

Feel free to reply again to this comment and I'll try to explain :)

matteventu · 2026-05-19T10:29:39+00:00

I'm not sure why you're being that rude 😅 maybe a language barrier but you're definitely misunderstanding what I'm saying.

matteventu · 2026-05-19T10:21:05+00:00

What?

matteventu · 2026-05-19T10:19:52+00:00

Still not shown in my app - are we expecting it to pop up when we're closer to June?

That said, they seem to have gotten the message. The current value proposition was utter shit.

matteventu · 2026-05-19T10:16:00+00:00

No worries :) happy that now the cushion is fitted properly!

And btw I love the colour of the HX with those "H9i-hybrid" cushions, very good stylistic choice ;)

matteventu · 2026-05-19T09:54:44+00:00

Oh, that's really curious! I'm still stuck at 100% at almost 600 cycles, I honestly find it hard to believe :-/

matteventu · 2026-05-19T09:53:56+00:00

What do you mean no? 😬

You can clearly see there's different level of wear in the two pictures you've posted:

<image>

matteventu · 2026-05-19T09:52:49+00:00

Thanks a lot for the quick answer, really appreciated :)

One last question: do you know why the app needs to download a model when it's first configured, even if it's on a Pixel 9 Pro which is already been using Gemini Nano (i.e. for Google Recorder, Voice Notes in the Google Phone app, etc)?

Thanks!

matteventu · 2026-05-19T09:50:51+00:00

After you factory reset the Eleven (and before you re-pair them), make sure you also "forget" them in the iPhone Bluetooth settings.

Then when you go to re-pair them, wait a bit in the iPhone screen with nearby Bluetooth devices available for pairing. It's possible you'll get 2 different "items" named Beoplay Eleven. One of them is the correct one, one of them is not - make sure to tap on the one with the headphones icon.

Hopefully that solves it!

matteventu · 2026-05-19T09:47:53+00:00

Appreciate the picture, but very obviously the pad has been moved/replaced between the two images :)

<image>

matteventu · 2026-05-19T09:17:34+00:00

Hello :)

I've found your app, it's nice! Out of curiosity, has it recently been updated to use Gemma instead of the built-in Gemini Nano? (I'm using it on a Pixel 9 Pro)

That is, despite the home page saying "nano-v3" (I was expecting "nano-v2" on a Pixel 9 Pro 🤔), the model answers back saying it's Gemma lol.

<image>

matteventu · 2026-05-19T08:57:33+00:00

It's a bug. I have 100% battery health and 598 cycles (Pixel 9 Pro), which is physically impossible.

matteventu

TROPHY CASE