acc VS caddy-dynamicdns

Started using acc a month ago. Everything was ok, but at one point the phone crashed, I hard-restarted it, and then it started bootlooping. Now it looks like the phone no longer charges at all.

If you choose to root your phone, there is always Acc . It's fantastic, you cannot set it to stop at a %, I haven't had luck with that, but I have had luck with setting it to stop at a voltage. Use AccuBattery (free) to monitor the voltage and figure out what's battery voltage = the % you want to stop at. On my Pixel 7 Pro 85% is about 1.260

Improve battery longevity with Advanced Charging Controller Easiest way is to use AccA on F-Droid, a GUI/Front end that it installs and configures ACC My config; // Charge level limited to 80%, Charging Current to 700mA & the Charging voltage to 3800

Advanced Charging Controller somehow had a bug where it didn't allow the phone to take a charge. Unfortunately, I didn't catch the issue until my phone died. It still doesn't charge, and it's not recognized by fastboot or edl tools. Is there anything I can do to revive it?

Can use acc (Root required) using termux and hence can be automated.

Yeap. You can always root the device and install ACC (https://github.com/VR-25/acc) using Magisk.

There is also a Magisk module Advanced Charging Controller , which automatically stops charging when at certain percentage to save the battery.

This plugin for dynamic DNS: https://github.com/mholt/caddy-dynamicdns, supports any of these DNS providers you find on this page https://github.com/orgs/caddy-dns/repositories?type=source. You can use DuckDNS for example which is also a free domain.

Sure, you can do this with nginx and dynamic DNS if you really want to, but Caddy does it all for you, with automatic HTTPS, and runs natively on Android (or in Termux): https://caddy.community/t/running-caddy-2-on-android/13993?u...

Here's the dynamic DNS plugin: https://github.com/mholt/caddy-dynamicdns -- it will just update the A records for your domain directly with your DNS provider, no need for a third-party service.

Re 3: What you really need is Caddy [0] with this dynamic DNS module: https://github.com/mholt/caddy-dynamicdns

Caddy has state-of-the-art certificate automation and TLS support, and with that module, it automatically updates DNS records if users have non-static IPs. It'll also serve certs for localhost domains (use *.localhost IMO).

[0]: https://caddyserver.com (I'm the author, for disclosure)

Caddy has a (WIP) dynamic DNS module that will keep your records updated for you: https://github.com/mholt/caddy-dynamicdns

Neat. I had a similar frustration so I wrote a dynamic DNS module for Caddy; https://github.com/mholt/caddy-dynamicdns - it can be extended to work with any dns provider that has an api. (It's what I currently use with Cloudflare)