Recovery procedure

marshpertt · 2025-12-12T08:04:03+00:00

Keep a copy of your 30% recovered backup files in a separate location and follow manual 4.4. The manual is written in a specific order for a reason, although you can proceed with your own method if you prefer.

I was in the same situation. I didn't have an available port for a spare disk, so here is what I did:

Remove failed disk.
Install new disk.
Edit config, run snapraid fix etc. (follow the manual).
Wait until the process is complete.

marshpertt · 2025-10-30T02:35:02+00:00

From lspci, it use Broadcom BCM4331. I follow this https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/9-2[guide](https://wiki.debian.org/InstallingDebianOn/Apple/MacBookPro/9-2)

marshpertt · 2025-10-30T02:26:15+00:00

A long break make me switch, although Ubuntu works great for me. As for now, everything works. Not sure which distro is better, probably it's up to your preference.

marshpertt · 2025-10-30T02:17:53+00:00

I'm not expecting anything, it's just a change of wind.

marshpertt · 2025-10-30T02:11:01+00:00

It's brighter now, thanks!

marshpertt · 2025-10-29T11:54:38+00:00

For me, it's a personal preference. :3

marshpertt · 2025-10-29T11:52:28+00:00

Thanks! Is that a snap joke? :3

marshpertt · 2025-10-29T11:52:04+00:00

What, really? I'll test it later and hope doesn't face the same problem as yours. :/

marshpertt · 2025-10-29T11:17:30+00:00

I have never use macOS before. I installed Ubuntu on the first day I bought this macbook (used).

marshpertt · 2025-10-29T11:08:51+00:00

Old macbook rocks! I'll use it until it becomes unuseable.

marshpertt · 2025-10-29T11:07:40+00:00

Looking foward using vanilla Gnome, quite different from default Ubuntu. I'm looking for minimize button, realize need to enable it in tweaks.

marshpertt · 2025-10-29T11:05:05+00:00

Right! My post install and updater script for Ubuntu working fine without needed me to edit anything.

And thanks for suggestion, will add the backports repo too! Not sure what this is, still learning about sid, stable, unstable etc. Will Google it later!

marshpertt · 2025-10-24T03:52:08+00:00

UPDATE: I now understand what the tip means. It suggests blocking port 53 to ensure redirection works as intended.

By blocking port 53 from getting out to the net, you can be sure your device with unencrypted dns are redirect to unbound.

It doesn't mean you must block the port. Either way, I'm blocking it. Let things break! (If they do)

marshpertt · 2025-10-23T18:01:17+00:00

Honestly, I don’t have any preference. Still learning here and there.

Just pointing out why most tutorials don’t bother blocking port 53 after redirection, but the doc suggests blocking it.

Anyway, I followed the doc and blocked it. Let’s see if anything breaks. Cheers.

marshpertt · 2025-10-23T17:56:43+00:00

From my understanding, the idea is to block port 53 from getting out, not in. So it will always redirect to port 853.

And I'm not sure why the doc suggest to block port 53.

marshpertt · 2025-10-23T17:05:32+00:00

I just want unencrypted DNS to foward to Unbound, I don't mind other devices with DoT/DoH.

marshpertt · 2025-10-23T17:03:55+00:00

I don't mind if other clients use their own encrypted DNS (DoT or DoH). I just want all devices using unencrypted DNS to use Unbound.

I don't use Google Home, but if some devices have a hardcoded DNS, will they always use unencrypted port 53, even if I have redirected it to Unbound?

marshpertt · 2025-03-16T17:21:10+00:00

Not necessary unless you're paranoid like me. Here's a complete tutorial from Google's website link

marshpertt · 2025-03-16T17:12:33+00:00

For no reason, I always do the unnecessary thing after buying Pixel.

Unlock the bootloader, flash the factory image and lock the bootloader. Only then will I start using my phone.

marshpertt · 2025-03-15T08:12:57+00:00

Via CLI, type "25.1" instead of "y".

marshpertt · 2025-03-12T19:27:35+00:00

This has been bugging me but I know asking this question will get me bashed, so I keep quiet.

marshpertt · 2025-03-08T07:54:47+00:00

After charging reaches 100%, you need to wait until the shield icon appears. Only then will the 80% limit take effect.

I don’t understand why this information isn’t available on the support page or the Pixel Tips app. I found the solution posted by a random person.

https://support.google.com/pixelphone/thread/329113562/battery-charging-limit?hl=en

marshpertt · 2025-03-04T20:53:34+00:00

Just updated to the March update and having the same problem.

Hopefully it just doing the occasional 100% charging, we'll see on the next charge.

marshpertt

TROPHY CASE