Very impressive, even if broken on high refresh rate devices.
Very impressive, even if broken on high refresh rate devices.
Next time you can save yourself a reset by using adb.
adb shell "pm clear com.google.android.gms && reboot"
adb shell "am start -a android.bluetooth.adapter.action.REQUEST_DISCOVERABLE"
Also on my device (oppo watch), play integrity doesn’t seem to matter. Some of the time I’m only passing basic and watch works perfectly.
Most of them aren’t maintained anymore. Like Dialer, which lineageos patches up to work properly on newer versions (https://lineageos.org/Changelog-28/).
Pairdrop is probably a miracle tool for me. Just open the website and send files or text, no configuration, no fuss and it even works outside of the local network.
One day I’ll finally set up my own server, but that’s just for the fun of it. One hosted at https://pairdrop.net is super solid and I can’t remember it failing me.
I think android has this built-in. On mine it’s in Security & Privacy -> More security & privacy -> App pinning
…or maybe it’s just a custom rom thing (crDroid 10.4, Android 14).
Neo-Backup with special backups enabled can do that and much more. Works well with synchronization tools. Root required.
Since you mentioned it, there’s a fork of AntennaPod with a more modern look: https://github.com/XilinJia/Podcini
You know what? I never noticed that.
The stock files app is lacking to say the least. Try Material Files and optionally Round Sync which will allow you to access all rclone supported remotes in the material files app.
Also, it’s quite aggressively pushing the paid option without a way to turn that off
Neo Backup with special backups (SMS, wifi passwords, wallpaper) enabled. One downside is root requirement.
rathole aims to be somewhat of a replacement for CF tunnels. It was featured on noted some time ago: https://noted.lol/cgnat-and-rathole/
Nice read!
I especially liked the part with the wiggly trace for better signal integrity. Always good to see design theory in practice.
Hey, I like YAML config just as much as the next guy, but I understand the decision to go the GUI way.
With large Home Assistant installs YAML gets really messy, and most changes require a reboot to show up (well, both issues could be fixed by the devs, but they chose otherwise). I really thought that I’d miss YAML, but so far it’s working just fine for me. Migration or restoring is a bit more tricky, as I prefer the start from scratch approach instead of the restore a 10 year old backup one.
Home Assistant’s (docker install) backup is just a zip file of the config folder. This makes it easier to fix things if needed, but isn’t as nice as editing YAML directly. I’d love to have option to use YAML if I want to and GUI otherwise.
As for developers being a bunch of assholes? Well, you’re right. Luckily the community is much better and much more helpful.
jtxBoard, open source, syncs over caldav (works great with Zanshin) and has very active developer.
Additional it supports Material You and has included notes and journal support. Oh, did I mention it’s free?
That’s good and not. The good thing is they found it, but the bad thing is that the autopilot still needs some work.
It’s not really an autopilot if it crashes after pilot ejects.
Sorry to hijack, but does someone have a link to the talk? Article mentions it, but link no longer works.
Apps and more (sms, wifi networks, bluetooth devices), free and open source: https://github.com/NeoApplications/Neo-Backup