u/YourBuddySal

Random drops to 0 B/s when uploading

I'm using Nicotine+ on Windows 11. As pictured in the gif, during any normal upload, speeds will randomly drop to 0 B/s.

Is this normal? If so, it's chill. I host a lot of files that are 1-3 GB that are often downloaded in groups of 50-100 files at a time and I think it'd be great if uploads were more stable on my end. I have fiber with 1Gbps up and down and would like for it be fully utilized if it's possible.

Thanks so much!

u/YourBuddySal — 13 days ago

Can't see user profile from another user on the same network

I'm using Nicotine+ on both mine and my roommate's computer and I'm unable to see his profile and he's unable to see mine.

For more information, he's on Windows and I'm on Linux. We're on separate sharing ports and I've opened the ports on the router and firewall for each of our computers. People outside of our network download files we're sharing. The 'check port status' from the Nicotine client also shows 'open' for both computers.

I don't know if it's a configuration issue or the issue is that we're both on the same network. Any ideas why this might be happening? I have an inkling that it's because it's from the same IP address, but I figured I'd ask to see if there was something else going on.

Thanks for the help!

reddit.com
u/YourBuddySal — 2 months ago

System updates not going through.

Hello! I'm setting up an Asahi Linux install on an M1 Macbook Air and I've noticed a certain system update won't go through. (This is my first time with Asahi or Fedora or even a Mac! :P)

I probably ran it about 5 times and it keeps showing up with this. Any idea as to why this might be happening? I also tried running dnf updates and upgrades from the terminal and update-m1n1.

I'm more familiar with Arch and Pacman and I don't know DNF or Gnome Software very well. Any help or advice would be appreciated! It's not a major issue, but the little blue updates available notification is bugging me lol

u/YourBuddySal — 2 months ago
▲ 1 r/tasker

[Advice] Autowear Heartrate Polling Battery Usage

Hello!

I use Autowear (Pixel Watch 3) to poll my heart rate every 2 minutes and log it. To ensure that it doesn't timeout, I have the screen turn on before polling. This has worked really well and rarely misses a poll. However, it does take a big ding in the battery life. The watch normally gets ~36 hours when I'm not running this task, but it drops to ~20 hours when the task is running.

I know doing this will make the battery life inevitably take a hit, but if I could get ~24 hours of battery life, that'd be ideal, because sometimes the watch dies when I'm sleeping and I'd like to charge it once a day.

Does anyone have experience with balancing heart rate polling and battery efficiency? I was wondering if there was any other option outside of turning the screen on to guarantee the polling measurement is taken.

I'm okay with where things are at, but I figured before I put this project to a close, I'd check if anyone had a magic bullet for balancing decent battery life and heart rate polling with Autowear.

Thanks so much!

reddit.com
u/YourBuddySal — 5 months ago