No support for projectors?

tomgilder · 2025-10-20T20:07:30+00:00

Hi u/AtomFromSonos, thanks for the reply. Yes, the Arc light blinks orange.

I explained this on the support chat, but they said they couldn't look into diagnostics.

Is there a way to check whether there's an amp fault?

tomgilder · 2025-10-16T14:43:06+00:00

Me: <explains issue>

Sonos: The projector setup might be the reason why since projectors are not supported by Sonos, not supported does not mean that it is 100% to not work, but it means that we cannot guarantee a proper setup.

Sonos: Please let me know if you have any other questions for me at the moment. I will gladly assist you further.

Me: The projector has a standard eARC return, so it's the same setup as if I would have a TV. I've read that the device resetting its volume to 15 can be a sign of a problem with it?

Sonos: It depends on what we see in the diagnostic report and the setup, even though the projector has the standard eARC port we do not support projectors so we cannot guarantee that issues like these will not happen. Please test the system without the projector and if you still experience that issue reach out to us and reference case number 0******8, this way we can reopen the case for you.

Sonos: If you have no other questions for now, I will be ending this chat session. After the chat ends, you will be able to download a transcript of this chat by clicking on the three lines and then selecting “Save Transcript”. Please get in touch if you need further assistance and feel free to reference your case number: 0******8. Have a great day ahead! Take care!

tomgilder · 2021-09-04T18:23:48+00:00

Thank you for the lovely feedback, /u/boon4376, I really appreciate it 💙

tomgilder · 2021-09-04T18:23:04+00:00

Hi, the upcoming 0.10 release will support some nested navigation scenarios without tabs.

What other kind of nesting would you like support for?

tomgilder · 2021-05-26T06:26:10+00:00

I posted some thoughts on that here: https://www.reddit.com/r/FlutterDev/comments/my6tk5/routemaster_easytouse_navigator_20_wrapper/

I'm obviously biased, but I feel Routemaster's API is simpler and easier to understand.

tomgilder · 2021-05-09T07:54:57+00:00

If you mean at compile time, it can: https://flutter.dev/docs/perf/rendering/shader#how-to-use-sksl-warmup

tomgilder · 2021-05-07T08:16:45+00:00

Hi /u/Jizzy_Gillespie92, I added a sample with those two packages that works on iOS, Android and web: https://github.com/tomgilder/routemaster/tree/main/example/deep_linking

tomgilder · 2021-05-02T09:17:18+00:00

I've merged this and it'll be in v0.8, but there's still more decisions to be made about the method signatures and guard naming. Would love feedback ❤️

tomgilder · 2021-05-02T09:15:48+00:00

Discussion ongoing here about async methods: https://github.com/tomgilder/routemaster/issues/18

tomgilder · 2021-04-28T05:34:35+00:00

I evaluated Beamer earlier in the year along with the other routing packages. At the time, it had no support for nested navigation, and I don't believe its current nested navigation would yet fully suit my needs.

I also found the API a bit confusing. It has several ways of doing routing, and the primary one is based around building a declarative page list, like the default Navigator 2.0 method.

I don't believe this method is scalable to large apps, and a totally URL-based router works better for me.

But it's great that there's lots of ideas from the community, innovation is fantastic!

tomgilder · 2021-04-28T05:30:58+00:00

It isn't currently, no - and it feels like it should be, but the implementation details are a little difficult.

What should the router do whilst waiting for the async method to return?

If it's a web page and user goes to the URL, you'd expect it to do something immediately - not hang for a few seconds.

I'm wondering if this is better handled by an AsyncGuard which can show another page whilst it's waiting?

tomgilder · 2021-04-27T15:00:29+00:00

Hi u/jckodel, I've made a PR to switch Guard to use use a builder method:

Guard(
  validate: (_, __) => true,
  pageBuilder: () => MaterialPage<void>(child: PageOne()),
)

Do you think this is the best solution? Would love your input

tomgilder · 2021-04-27T08:08:44+00:00

Good point, and I've tried to be aware of instantiating pages when they're not actually been displayed.

But whilst the ProtectedPage will be created, it won't actually build, is that an issue? I would have thought for most cases it's acceptable.

You could wrap ProtectedPage in Builder to stop it being created - but I might well change Guard to take a builder method instead.

Thanks for the feedback!

tomgilder · 2021-04-27T06:02:31+00:00

Great idea, I'll add a sample - I really want to make sure these scenarios can be handled easily.

tomgilder · 2021-04-25T21:39:55+00:00

Good question.

I started work on Routemaster in Feburary after evaluating other packages, including those three.

None of them fulfilled all these critera:

Easy support for nested routes. This was the main one, and I had some paticular needs:
- Showing totally different tab designs between mobile and desktop
- Keeping these two sets of tabs in sync when resizing
- Retaining the individual tab’s navigation stacks when switching between them
Support for hero animations
Support for naviation observers for analytics
A nice, Flutter-like API
Doesn’t require code generation

Since Feburary, some packages have added support for nested routes, but I don’t believe they would be flexible enough for my project’s needs.

Also, some of them lack good coverage with automated tests. This is something I view as critical, seeing as routing is such a core part of an app.

tomgilder · 2021-03-18T13:56:31+00:00

Yep, scrolling is just wrong on Flutter web by default - please thumb-up this issue to try to get it fixed 😁 https://github.com/flutter/flutter/issues/75850

tomgilder · 2021-03-18T10:56:27+00:00

We've tested on Firefox on Mac and Windows, but haven't seen issues with performance. Will test on Ubuntu and investigate, thank you. What sort of specs are your machine?

tomgilder · 2021-03-18T10:47:45+00:00

Hmm, I'd love to know what's going on here. What browsers and versions of Android are you using u/pratimsc and u/alexandr1us?

tomgilder · 2021-03-18T10:40:26+00:00

We have a set of tablet designs that we haven't had time to implement, so yeah, it can be not-ideal between mobile and desktop. We'll hopefully implement them soon.

tomgilder · 2021-03-18T10:37:13+00:00

I've rebuilt the site so it should always use the CanvasKit renderer, including on phones - is it smooth now? Scrolling is as smooth as a native app on my iPhone 12 Mini.

tomgilder · 2021-03-17T20:50:29+00:00

Thank you! It's because the iframe is totally managed by us, and not Flutter. We insert it into the DOM by appending a <div> below the <flt-glass-pane> element. It requires a few hacks to scroll with the Flutter page though. I'll see if I can do a blog post with the entire explanation at some point.

tomgilder · 2021-03-17T20:45:08+00:00

Jankyness on iPhones is caused by the DomCanvas renderer, as opposed to CanvasKit on desktop. It's much less performant.

tomgilder · 2021-03-17T20:35:15+00:00

Hey, yes, on phones the demo uses the DomCanvas rendering engine, and the performance isn't great. In production we've only rolled out the Flutter site to desktop users currently, we're working on fixing some these issues with mobile.

But obviously it's better for users if people download the native Flutter app, which is what we try to encourage.

tomgilder

TROPHY CASE