Search results

Basically you need to reset the phone from the OS and NOT enter any pin because otherwise it'll be encrypted.

Tbh that's the main reason I switched over to the PixelExperience Plus builds. Requires a full wipe but worth it IMO.

If we're lucky it'll get fixed with the new beta builds.

Haven't heard back anything yet so my best guess is that there's nothing I can really do.

I haven't sadly. I've already switched to a different ROM for now. Keeping things fresh is always nice in that regard.

Update on MIX 4: still broken (as expected) Will try PixelExperience or something, always liked Pixels in terms of feel.

Updating MIX 4 right now, don't have too high hopes but I may try other custom roms if it doesn't work in the meantime :)

To be honest, at this point I'd be willing to lend the devs my MIX 4 so they can fix the issue.

I may attempt to update again today

I once again ask the devs to let me give them my MIX 4 to fix the notification issue

Anyone brave enough to try a clean install on a MIX 4?

Anyone tested a fresh install of this build on their MIX 4?

Would it be a possiblity to send a mix 4 to the devs to fix the notification issue? I'm talking personal device

I'm on stable already. I'm just hoping for the issue get fixed so we can get another stable some time.

Is there any way for devs to get their hands on a MIX 4 to fix the still-persisting notification issue?

Update: downgraded to 22.5.11 due to google sync service issues affecting calendar and other apps like dialer and contacts. Notifications are working fine when upgrading from ~22.3.16 on MIX4, seems like us MIX4 users are back in the green again.

The weird part is it worked fine before upgrading, but every time I want to open the calendar I need to force-close the calendar provider first. Also I need to keep enabling the calendar provider via ADB, since it keeps getting disabled by itself. I can probably provide a log tomorrow if needed...

Getting this bug recently when trying to open Google Calendar with Niagara Launcher. If I re-enable it via ADB shell with pm enable com.android.providers.calendar it seems to work sometimes.

Going to take a leap of faith and upgrade my MIX 4 from 22.2.23 now to this 22.5.18. Will report back how it went. If the notification issue still persists for me I'm going to run the Stable builds from then on. EDIT: after ~30min everything's still looking good, will report back tomorrow.

Anyone with a MIX 4 wanna try and see if the notification/network issues are fixed?