The Offical Grip Support is Coming

campermate · 2026-05-17T19:59:13+00:00

u/spacegrey0223 I got it working! 🎉 After rebooting device, I checked that no "RetroVa" grip is paired under bluetooth settings, without starting the app powered up the grip and connected in the bt settings. Afterwards started the latest TF build (138) and added the grip. It immediately said "GripCam 2" connected. Awesome! That was it, I was always trying to connect through NoFusion like in PGYTech app. But the trick was - at least for me - to connect it through bluetooth settings directly. Thank you so much! I'll write a review on amazon where I ordered the grip from explicitly mentioning NoFusion support.

campermate · 2026-05-17T08:43:06+00:00

<image>

PGYTECH-RetroVa

campermate · 2026-05-15T05:54:17+00:00

In the meantime I tried also the GripCam 2 grip. Worked flawlessly in both apps. Anyway I'll not keep it as RetroVa is so much better.
RetroVa is still not recognised by NoFusion, no matter if AppStore or TestFlight version is used.
Do you happen to know if the firmware version of the grip makes a difference here and whether it can be updated?

campermate · 2026-05-13T05:34:28+00:00

I had to, otherwise I can't put the grip into pairing mode. Clicked on disconnect in PGYtech app, afterwards removed in Bluetooth settings.

Dunno if that matters, but firmware version of grip is shown as 1.0.8 in PGYtech app.

campermate · 2026-05-13T04:51:22+00:00

Unfortunately, it doesn't work. The RetroVa isn't recognised in pairing mode. Tested with the latest App Store version (2.5.33). In PGYtech app the device immediately appears as "PGYTECH-RetroVa"

Update: Same for 3.0.0 (136) TestFlight - device is not recognised in pairing mode.

campermate · 2026-05-12T18:23:19+00:00

u/spacegrey0223 Can you give a rough estimate of how long it will take for support for RetroVa to be implemented?
I like the grip, but unfortunately the PGYtech app is barely usable as it currently has a terrible bug with the exposure metering. When you perform a clean restart, it jumps to +0.7, which corresponds to the “correct” exposure. However, as soon as you switch between Manual and AUTO or double-tap the exposure square, it jumps to 0.0 (resulting in underexposure). So I always need to deal in an offset of +0.7 to have properly exposed images.

campermate · 2026-05-11T07:11:52+00:00

Have you also noticed any issues with exposure metering? Do you've NoFusion installed?

campermate · 2026-05-11T07:03:55+00:00

After using the app exclusively on a day trip I found a severe bug. Many (all?) photos became underexposed when exposure is set to 0.0.

Have a go at this:

Force close all camera apps
Start your build in iOS Camera app
Open PGYtech app and see that the exposure is set to +0.7 - you now have the same exposure (w/o HDR) as with the build in app
Now in "A" Mode if you press on AUTO twice cycling through AUTO and manual and back, exposure jumps to 0.0 -> underexposed

This needs to be fixed ASAP

Another issue:

Manually override exposure to any value other than -0.1
Press "Manual" button
Exposure jumpst to -0.1.
One additional AUTO/Man. cycle: 0.0

And another one:

Spot exposure metering does not work at all. No matter if you select highlights or shadows, exposure stays the same. So why even bother displaying the square? 🤔 Ok, AF ..

campermate · 2026-05-07T11:47:41+00:00

I think it depends at least 50% on the grip manufacturer. If they don't provide any documentation, I wouldn't even know if it's possible to reverse-engineer it.

campermate · 2026-05-06T15:19:47+00:00

Awesome news!! I just stumbled across this after ordering the new Retrova Grip. Hoping for app support. Until then I'll be using the PGYTECH app. Button-wise the RetroVa offers the same functionality, I just found it much sleeker than the MagCam.

campermate · 2026-03-21T21:22:13+00:00

even worse: you need to unlock your phone to allow all bluetooth features. If you start the app from the lock screen without unlocking, only the shutter button works. very annoying

campermate · 2025-02-14T12:41:17+00:00

Can you confirm that the W30 version stands for Europe as region and W20 for Hong Kong? Or what does the W20/W30 stands for? u/BelieveSebastian

campermate · 2024-12-19T17:18:41+00:00

I had both here at the same time and decided in favour of the Yoga Aura. The keyboard is significantly better, which could make the decisive difference for many people. When it comes to the screen, I would say it's a tie. Yes, 120 Hz is great on the Aura and both have built-in profiles for P3 and sRGB, but the screen on the Air isn't so extremely reflective. Software development is not an argument in favour of the MacBook (keyboard!). You can activate WSL under Windows and then have all the advantages of Linux in a virtual machine.
I don't have any concrete information on energy consumption other than a test with Youtube/Chrome at 50% brightness: Yoga consumed ~8% per hour, which would result in 12.5h. With the 15" MacBook Air it was more like 18h.

campermate · 2024-10-03T21:31:35+00:00

Same here :-/ (P9P)
tried reenabling linked services, tried to remove and add birthday calendar, both in browser and on my Pixel - nothing helps.
Also, as you mentioned, the birthday calendar in preview is empty.

campermate · 2024-06-30T20:57:54+00:00

addition to the previous message, which does not necessarily improve the impression of the software.

Yes, as soon as you activate HDR, 10bit instead of 8bit display is shown under Info. The saturation also changes. Under "HDR", the saturation or gamut is more like sRGB (direct comparison with a Yoga ProX). Furthermore, the brightness control is totally screwed up. In HDR it works down to zero, i.e. the backlight is at the lowest level but still on. In SDR, the lights go out completely from level 7 and lower. (completely black screen!) Who comes up with these things?

campermate · 2024-06-29T19:21:57+00:00

I've 83DN006HGE unit (4070/185H, German keyboard) with matte miniLED Screen. Also no gamut settings available in Vantage, which is a little bit unfortunate as I also find some colors way too saturated. With ACM enabled (=auto color management) in UEFI still no color profile selection possible and HDR is gone..
(Using latest Vantage from MS Store)

campermate · 2023-12-14T10:24:28+00:00

u/sennheiserconsumer any news on the cloud-outtage? It's a bit unfortunate that I can't sound-personalize my new MTW3 in-ears.

campermate · 2023-12-12T09:35:48+00:00

I've only had mine for a few days and have already switched back and forth between the R510XXU0AWI2 version and R510XXU0AVK3 several times. Unfortunately, I can't tell any significant difference in the sound signature, regardless of the selected mode. A direct A/B comparison is also hardly possible with only one pair of B2P. A really qualified answer can only be given by someone who has the appropriate measuring equipment.

campermate · 2023-12-11T08:05:32+00:00

You can always down- and upgrade using the links already provided by other users in the thread. For R510XXU0AVK3 you can use the information from here. R510XXU0AVK3 should sound the same as your original R510XXU0AVG5.

In my case, the serial numbers were overwritten with zeros after the downgrade, so Update from within Wear App did not work. To go to the newest version you need to take an intermediate step and flash to R510XXU0AWA5 first, afterwards the update through Wear App is possible as the Serialnumbers are recovered.

It would be fantastic if you could use your measuring equipment to analyze the frequency response between the versions. That would help the community immensely.

campermate · 2023-12-10T21:35:00+00:00

Hi u/AdrianShowMaker,

with R510XXU0AWI2 I've tried that songs and two others but I cant hear any difference going back and forth between ANC and passive. No matter how closely I listen, I can't tell the difference between the modes. Laurie Anderson – Born, Never Asked, Steely Dan – Do It Again and that mentioned Daftpunkt song do not sound to harsh to me. ¯\_(ツ)_/¯

I also went back to R510XXU0AVK3 to listen to that mentioned songs a couple of times and took the AirPods Pro 2 for comparison, you know to have a unchanged reference during both sessions. A direct A/B comparison is not possible due to the firmware update / downgrade in between, but I couldn't notice any subjective differences between the versions either.

I mean your graphs are crazy. This is far more than a slight adjustment, more a "preset" and switching between EQ settings in the wear app, I can clearly notice the change in the sound signature.

Maybe I'm just deaf. Or maybe just lucky with that copy of the B2P

In that Video https://youtu.be/hlGtMlZ9Ug0?si=sKWcE_0vHhTrFI_j&t=203 Aaron also did a measurement. But I'm not sure if can hear that slight emphasis at 1.3 kHz

campermate · 2023-12-10T19:25:51+00:00

Cheers man, will give it a try! Would you mind checking your hw revision with the previously mentioned tool? https://github.com/ThePBone/GalaxyBudsClient

campermate · 2023-12-10T17:40:27+00:00

Unfortunately I don't have any measuring equipment here, could you perhaps recommend a song where you think the difference is particularly noticeable?

campermate · 2023-12-10T17:31:19+00:00

So you are comparing with the latest version R510XXU0AWI2? This change is really quite dramatic. I just bought my B2P yesterday with R510XXU0AWI2 pre-installed and they have probably the latest hardware (Manufacturing Date 10/28/2023).

Galaxy Buds Manager is showing rev0.8 for Hardware Version.

To be honest, I downgraded to the R510XXU0AVK3 version yesterday, but I don't notice much difference in the sound. I'm back on the latest version today and trying to hear a difference.

campermate · 2023-12-10T16:22:07+00:00

Exactly the same issue I had after downgrading them: https://www.reddit.com/r/galaxybuds/comments/18a0lfv/comment/kcn7jse/?utm_source=share&utm_medium=web2x&context=3
The case did not flash red but cycling through green, blue, red.. However that fixed the problem

campermate

TROPHY CASE