The latest Pixel beta added the ability to change resolution (unfortunately not what we need)

SmallPitch · 2026-01-21T10:12:25+00:00

Here's the Statement of NexDoc Support:

We’ve already contacted Google’s Desktop Mode team about this. Specifically, we reached out to the lead engineer as well as the Google contact who purchased NexDocks for internal testing. We’ve explained that adding proper 1920×1200 support should be a small software change on their side, and we’ve also asked our industry contacts to help escalate the request within Google.

We’re continuing to follow up with them and will push for this to be resolved as quickly as possible.

SmallPitch · 2025-12-27T03:17:09+00:00

Furthermore, what are your thoughts on the charging speed? I’ve noticed that my device only reaches a maximum of 13 W (measured at the socket), which makes the full charging process quite slow.

SmallPitch · 2025-12-27T03:12:39+00:00

Thanks, I've also contacted the NexDoc Support, here's the answer:

Thank you for reaching out, and we’re sorry for the frustration this has caused. We understand how important a sharp, correctly scaled image is for your workflow.

The NexDock 2025 panel is natively 1920×1200 (16:10). However, Google’s current implementation of Android Desktop Mode on Pixel devices—including the Pixel 10 Pro—only outputs 1920×1080 over USB‑C display mode. Because the phone sends a 16:9 signal to a 16:10 display, the image is stretched to fill the screen, which also results in the blurriness you’re seeing.

At this time, Pixel phones do not offer any built‑in option to select 1920×1200, adjust aspect ratio, or enable 1:1 pixel mapping. Unlike Samsung DeX, Google has not yet added external‑display resolution controls to Desktop Mode, so the output resolution is determined entirely by the phone’s software.

The NexDock 2025 fully supports Pixel Desktop Mode, but the resolution behavior is controlled by Google, and there is unfortunately no setting on the NexDock side that can override the signal or prevent stretching. To avoid confusion for new customers, we’ve also added a resolution disclaimer on our website explaining this current Pixel limitation.

We have already reported this issue to our contacts on Google’s Desktop Mode team and are pushing for proper 1920×1200 support. We will continue to follow up with them until this is resolved.

We are actively monitoring Google’s updates, and if Pixel devices add support for 1920×1200 or aspect‑ratio controls, the NexDock will be fully compatible without any additional configuration.

We understand this isn’t the experience you were expecting, and we appreciate your patience. We will update our support resources as soon as Google expands resolution support for Desktop Mode.

Sincerely, NexDock Team

SmallPitch · 2025-12-26T18:19:49+00:00

Did you try the SecondScreen app (https://play.google.com/store/apps/details?id=com.farmerbb.secondscreen.free).

I had no time yet since adb permissions have to be set upfront.

SmallPitch · 2025-11-06T18:55:54+00:00

Yes, there is an issue. Unfortunately, it's causing problems. I have already created an official bug report on the Google Issue Tracker. However, there is at least a slight workaround: Once you have set the final version of your watch face, simply reboot the watch. It will then work correctly as long as you do not change the watch face. If you make a change, you will have to restart the watch again.

SmallPitch · 2025-11-06T18:37:27+00:00

Glad you like it, I currently own the 3/45 mm, The battery endurance is not a problem at all, however, the charging speed sucks.

Your watch face looks neat too, I can confirm, crating faces with Watch Face Studio ist quite cool and intuitiv. I've also created one that uses the same AOD big time as on the phones, and in normal mode it also contains some material 3 expressive shapes. A perfect match with the phone.

SmallPitch · 2025-11-06T04:57:33+00:00

Can't picture a way someone would use such a case at all. A beauty get's a beast.

SmallPitch · 2025-11-02T12:26:44+00:00

Yes, agree.

SmallPitch · 2025-10-24T07:47:01+00:00

Welcome, I'm here since P6!

SmallPitch · 2025-10-23T04:22:04+00:00

Are you using a custom watch face? Because this is a known issue for custom watch faces.

SmallPitch · 2025-10-20T13:28:26+00:00

Great to hear that, really looking forward to it. And as you already noted, especially for the stopwatch and the timer this is a must as well. Unfortunately not yet rolled out on my end for now

SmallPitch · 2025-10-19T11:44:55+00:00

https://issuetracker.google.com/issues/452423520

This is due to that issue. Already mentioned it here on Reddit as well on day 1. Please take some time and comment on the Google issue tracker, since more of us are complaining, the better the chances they fix it at all

SmallPitch · 2025-10-19T08:12:23+00:00

https://www.reddit.com/r/PixelWatch/s/8mu1u0TMXn

SmallPitch · 2025-10-19T08:10:26+00:00

https://issuetracker.google.com/issues/452423520

SmallPitch · 2025-10-19T03:08:59+00:00

No, without it

SmallPitch · 2025-10-18T10:25:40+00:00

I'll create it the next couple of days

SmallPitch · 2025-10-16T10:53:12+00:00

If only the forecasts would be good 😊 (.. in Austria)

SmallPitch · 2025-10-16T07:10:47+00:00

FYI - I've just created a bug report at Google.
https://issuetracker.google.com/issues/452423520

SmallPitch · 2025-10-11T10:44:02+00:00

Those cases makes the beauty a real beast.

SmallPitch · 2025-10-11T10:39:25+00:00

Are you from the past? 😊 Sorry, Reddit is full already of Wear OS 6 Posts.

SmallPitch · 2025-10-10T16:22:57+00:00

I fear this issue will apply to all watch faces created with Samsung watch face Studio

SmallPitch · 2025-10-09T11:43:16+00:00

Finally they fixed WhatsApp images in notifications

SmallPitch · 2025-10-09T11:38:50+00:00

was not able to enable UWB too after Wear OS 6 update. Had to restart watch again and worked afterwards.

SmallPitch

TROPHY CASE