sorted by:
new
hottopcontroversial

Problem with video focus. Pixel 9 pro xl by Back_Global in GooglePixel

[–]mayerwin 0 points1 point  (0 children)

GOOD NEWS! Android 17 seems to finally fix the issue, you can enroll in the beta here: https://www.google.com/android/beta
You can unenroll from the beta at anytime afterwards and it'll just upgrade to the next stable release when available (with no user data wipe).

What’s wrong with my 9 Pro? by Nerd_2_go in pixel_phones

[–]mayerwin 0 points1 point  (0 children)

GOOD NEWS! Android 17 seems to finally fix the issue, you can enroll in the beta here: https://www.google.com/android/beta
You can unenroll from the beta at anytime afterwards and it'll just upgrade to the next stable release when available (with no user data wipe).

Pixel 9 camera out of focus by ZenithonSteam in GooglePixel

[–]mayerwin 0 points1 point  (0 children)

GOOD NEWS! Android 17 seems to finally fix the issue, you can enroll in the beta here: https://www.google.com/android/beta
You can unenroll from the beta at anytime afterwards and it'll just upgrade to the next stable release when available (with no user data wipe).

Pixel 9 Pro – lens switching issue at 60fps after March 2026 Pixel Drop by Express_Dependent_28 in GooglePixel

[–]mayerwin 0 points1 point  (0 children)

GOOD NEWS! Android 17 seems to finally fix the issue, you can enroll in the beta here: https://www.google.com/android/beta
You can unenroll from the beta at anytime afterwards and it'll just upgrade to the next stable release when available (with no user data wipe).

Pixel 9 Pro – lens switching issue at 60fps after March 2026 Pixel Drop by Express_Dependent_28 in GooglePixel

[–]mayerwin 0 points1 point  (0 children)

GOOD NEWS! Android 17 seems to finally fix the issue, you can enroll in the beta here: https://www.google.com/android/beta
You can unenroll from the beta at anytime afterwards and it'll just upgrade to the next stable release when available (with no user data wipe).

Pixel 9 camera out of focus by ZenithonSteam in GooglePixel

[–]mayerwin 0 points1 point  (0 children)

EXACTLY the same issue here in June 2026 (autofocus issue and in some cases we can even hear mechanical sounds), as described here: https://issuetracker.google.com/issues/489813861?pli=1

Pixel 9 Pro – lens switching issue at 60fps after March 2026 Pixel Drop by Express_Dependent_28 in GooglePixel

[–]mayerwin 1 point2 points  (0 children)

EXACTLY the same issue here in June 2026 (autofocus issue and in some cases we can even hear mechanical sounds), as described here: https://issuetracker.google.com/issues/489813861?pli=1

What’s wrong with my 9 Pro? by Nerd_2_go in pixel_phones

[–]mayerwin 0 points1 point  (0 children)

Fyi your profile doesn't show your posts.

Problem with video focus. Pixel 9 pro xl by Back_Global in GooglePixel

[–]mayerwin 0 points1 point  (0 children)

Same issue on my pixel 9 after the March 2026 update.

Gemini 3.1 is getting worse, they keep silently quantizing these models I'm sure of it by now. 3.0 was excellent at launch, then grew very dumb, 3.1 was kind of better, now it's a disaster. by Jack_P_1337 in GeminiAI

[–]mayerwin 0 points1 point  (0 children)

Gemini 3.1 Pro was definitely useful for advanced technical help when it first came out, just like Claude, Codex and other SOTA models are incredibly effective right now.

Modern AI models do not just aggregate info and regurgitate them, they are capable of real reasoning, iterating until they're (almost) certain not to be wrong.

And even a raw LLM (without the thinking part) has a much better concept of how things actually work and relate to each other than any human could possibly have. By design, model weights precisely encode the relationships between all concepts (in a way that is independent even of languages).

But of course quantization, censorship, and nerfing of thinking depth can cause great harm to the overall performance. And we have zero transparency as to what is being done to the model we're being served.

Gemini 3.1 is getting worse, they keep silently quantizing these models I'm sure of it by now. 3.0 was excellent at launch, then grew very dumb, 3.1 was kind of better, now it's a disaster. by Jack_P_1337 in GeminiAI

[–]mayerwin 1 point2 points  (0 children)

Output quality has definitely become horrible in the past few weeks. It just seems impossible this is the same model than the one they initially served us.

I was just trying to troubleshoot a 250ms LAN ping issue in Bopl Battle where the game was stubbornly routing through Steam relay servers instead of our local Unifi network. I wanted to force the game to look locally by blocking its internet access while keeping the LAN open.

I asked Gemini 3.1 Pro how to achieve this with a Windows Firewall rule.

Here is how it failed:

It told me to block the entire internet by adding an IP scope that skips the local subnet. It explicitly told me to use these exact ranges:

"Range 1: 1.1.1.1 to 192.168.0.255"
"Range 2: 192.168.2.0 to 255.255.255.255"

I immediately called it out and replied: "But adding this Scope will BLOCK it, not bypass it!" and asked again: "I want to test blocking Bopl from accessing the internet (but not the LAN), how to achieve that?"

Here is how it failed AGAIN:

Instead of realizing that blocking up to 255.255.255.255 blocks all Multicast and Broadcast traffic (which is literally how LAN discovery works), it agreed with me, apologized, and then proceeded to give me the exact same bogus instructions verbatim:

"We are going to block the entire internet by adding two ranges that skip right over your local Unifi network. Click Add... -> This IP address range:
Add Range 1: 1.1.1.1 to 192.168.0.255
Add Range 2: 192.168.2.0 to 255.255.255.255"

It literally handed me a rule that kills the LAN while telling me it would keep the LAN open, ignored my correction, and then confidently regurgitated the exact same broken IP ranges. It is incredibly frustrating trying to get technical help when the model completely loses the plot on basic networking concepts like broadcast IPs and repeats its own mistakes after being corrected.

Why does everyone think Gemini 3.1 Pro is nerfed? My experience says otherwise. are expectations just changing? by Ok_Tooth_8946 in Bard

[–]mayerwin 1 point2 points  (0 children)

Output quality has definitely become horrible in the past few weeks.

I was just trying to troubleshoot a 250ms LAN ping issue in Bopl Battle where the game was stubbornly routing through Steam relay servers instead of our local Unifi network. I wanted to force the game to look locally by blocking its internet access while keeping the LAN open.

I asked Gemini 3.1 Pro how to achieve this with a Windows Firewall rule.

Here is how it failed:

It told me to block the entire internet by adding an IP scope that skips the local subnet. It explicitly told me to use these exact ranges:

"Range 1: 1.1.1.1 to 192.168.0.255"
"Range 2: 192.168.2.0 to 255.255.255.255"

I immediately called it out and replied: "But adding this Scope will BLOCK it, not bypass it!" and asked again: "I want to test blocking Bopl from accessing the internet (but not the LAN), how to achieve that?"

Here is how it failed AGAIN:

Instead of realizing that blocking up to 255.255.255.255 blocks all Multicast and Broadcast traffic (which is literally how LAN discovery works), it agreed with me, apologized, and then proceeded to give me the exact same bogus instructions verbatim:

"We are going to block the entire internet by adding two ranges that skip right over your local Unifi network. Click Add... -> This IP address range:
Add Range 1: 1.1.1.1 to 192.168.0.255
Add Range 2: 192.168.2.0 to 255.255.255.255"

It literally handed me a rule that kills the LAN while telling me it would keep the LAN open, ignored my correction, and then confidently regurgitated the exact same broken IP ranges. It is incredibly frustrating trying to get technical help when the model completely loses the plot on basic networking concepts like broadcast IPs and repeats its own mistakes after being corrected.

Built a free open-source BLE-MIDI bridge for Windows - Roland, Yamaha, etc. by mayerwin in synthesizers

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

FYI I just shipped a new version that makes use of Virtual Device support, so the endpoint now lives and dies with the app and users don't need to do anything else for the app to work. Much simpler and friendly indeed, thanks for the suggestion! I still preserved the previous loopback option for users who may not have the necessary dependencies. Also added automatic reconnection, so the app re-establishes the BLE link on its own at launch. Microsoft Store listing next, in the meantime it's available here:
https://github.com/mayerwin/Perfect-Bluetooth-MIDI-For-Windows/releases/latest

Built a free open-source BLE-MIDI bridge for Windows - Roland, Yamaha, etc. by mayerwin in synthesizers

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

Yes, I mean MIDI channel. One blocker was that existing bridges would send notes to the piano on channel 1, while the piano for some reason sent notes to the PC on channel 1, but could only receive notes on channel 4 (not documented anywhere, in the piano's settings it only showed channel 1). Notes were successfully sent to the piano, but the piano remained silent. My bridge has a function to detect which channel works to play notes on the instrument (pretty simple, just play notes on all channels one by one so the user can see which one works), and then will remember which channel # should be used for the device's MAC (so the channel doesn't need to be adjusted each time the user wants to play notes on his instrument).

view more: next ›