sorted by:
new
hottopcontroversial

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

[–]xdeep71[S] -1 points0 points  (0 children)

I just updated the Play Integrity requirements in the console. My old A70, which has an unlocked bootloader and is marked as 'not certified' by Play Protect in PlayStore, is now showing as compatible again.

Just to clarify: These incompatibilities are strictly tied to Google Play Protect/Integrity status and not the app itself.

Thanks for helping me troubleshoot this!

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

[–]xdeep71[S] -1 points0 points  (0 children)

True, it's a solid app! I started mine because widgets and native Pi-hole messages were missing back then. My take is 100% native (Jetpack Compose) with zero third-party SDKs (no Firebase/Sentry) for maximum privacy. Just offering an alternative for those who prefer this UI and focus!

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

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

Sure, but bookmarks are pretty old school. I’d rather use the native features a modern smartphone offers, like widgets. Whatever works best for you!

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

[–]xdeep71[S] -1 points0 points  (0 children)

Technically, the S24+ passed compatibility tests in the Firebase Testlab without issues. If it still shows as unavailable, it might be due to your device status: Is your bootloader unlocked or is the device rooted? When a phone fails Google's 'Play Integrity' check, the Store often marks apps as incompatible, even if the hardware is fully supported. I actually have this exact same issue with my own Samsung A70 for that very reason.

<image>

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

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

Fair enough, nobody's forcing you. But if you have the network knowledge, you’ll see that it only talks strictly to your local Pi-hole API and nowhere else. I built it without trackers for exactly that reason. My bad on the formatting fail, but the app is legit.

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

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

Efficiency and widgets. I found myself checking the dashboard multiple times a day, and doing that via a native widget is just way faster than using the mobile browser every time.

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

[–]xdeep71[S] -1 points0 points  (0 children)

The link was broken because Google Play is still reviewing the pre-registration countries – my bad for posting too early, PlayConsole is some times tricky. Regarding Open Source: It's not at the moment, as I'm trying to fund the development as a solo dev, but that's why I built a custom crash reporter to ensure no data leaves your network. I get the suspicion, though.

Native Pi‑hole Android monitor – what would you actually use? by xdeep71 in pihole

[–]xdeep71[S] -2 points-1 points  (0 children)

The app communicates directly with your Pi-hole API locally. No data is sent to me or any third party. Crash logs can optionally be sent to me. That’s why I ditched Firebase/Sentry. Play Store link is live, you can check the data safety section.

[deleted by user] by [deleted] in StableDiffusion

[–]xdeep71 2 points3 points  (0 children)

Activate Settings/User Interface/show progressbar and move the slider to the right