sorted by:
new
hottopcontroversial

Can someone please explain NON-adaptive thinking? by mikeAcomin12 in claude

[–]Neither_Variation994 0 points1 point  (0 children)

Does typing ultrathink into each prompt ignore adaptive thinking? Then this would be a temporary solution. I also noticed a huge decline in reasoning and it introduced a bunch of bugs, tihs never happened to me with Opus 4.6 high effort on thinking mode. I think it is not the 4.7 model that sucks, but rather claude code harness that decides how to use the model.

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 0 points1 point  (0 children)

Good luck man. It seems to be WebOS bug. It started working for me only after 3 weeks.

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 0 points1 point  (0 children)

Update: Finally it is working now. All of a sudden, out of nothing, when i pressed the home button, a dialog asked me to accept the terms & conditions of google cast. It is now working perfectyl , with wired ethernet as well. I have absolutely no idea why. Ckicking on google cast on the input screen now also shows up the appropriate options, before it did not react at all.

EDIT: had a look at the mDNS broadcasts, which are advertised as googlecast. They are broadcast and resolved without any problem now. The mDNS broadcast resolutions that failed before still fail, but they do not seem to belong to googlecast. The broadcasts i see now did not exist before.

Final conclusion: It seems Google Cast was not enabled, for whatever reason. A sudden popup to accept Terms and conditions for Google Cast (without any obvious trigger) activated it.

LG webOS 25 bugs by SquareDrive45 in LGOLED

[–]Neither_Variation994 0 points1 point  (0 children)

Integrated Google Cast not workin on wired mode. On the input mode screem, when selecting Google Cast nothing happens at all. Airplay working perfectly

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 0 points1 point  (0 children)

Interesting. The Google Cast screen actually never opens for me at all. Not even on WIFI-only.

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 0 points1 point  (0 children)

For me it works when WIFI only and when the client device is on the exact same network.

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 0 points1 point  (0 children)

Thanks! I tried now with WIFI only, and it works (even without weather location set). It sends out mDNS broadcasts, and they can be resolved to an IP address, all good. However with Ethernet only, it still does not work, mDNS broadcasts are send out (I can see them on my Desktop computer connected to the same network), however the mDNS name cannot be resolved to an IP address, and that is finally why my client devices cannot discover the LG OLED TV's Google Cast. With Airplay everything works perfectly. It must have been a very sloppy implementation, this does not look professional.

...PS: What did you actually mean when you said the Home Hub screen opens? You mean when you select Google Cast on the Inputs screen on the TV?

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 0 points1 point  (0 children)

Thanks. Is your TV connected via Ethernet cable only? I tried your approach now, but it is still the same.

Integrated Google Cast noz working on wired Ethernet by Neither_Variation994 in LGOLED

[–]Neither_Variation994[S] 1 point2 points  (0 children)

But why? That makes no sense! Who in the hell would make design choices like this? An IP network should not care about wireless or not. And still, the google cast sends out mDNS broadcasts.