Depends on what I do with it. Usually the only noticeable drain is WiFi being active.
But for example encrypting and compressing large files will absolutely toast the phone.
The errors can be a problem, even if they aren’t written to a file. For example with tinyproxy. Disconnecting the network interface it’s running on won’t shut it down, it just keeps producing errors and clearly doing something as it can really heat up the phone.
This is what it spits out (as fast as it can):
...
ERROR May 25 13:01:06.107 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.107 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.107 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.107 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.112 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.112 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.112 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.112 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.112 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.112 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.114 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.114 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.114 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.114 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.114 [9701]: Accept returned an error (Invalid argument) ... retrying.
ERROR May 25 13:01:06.114 [9701]: Accept returned an error (Invalid argument) ... retrying.
...
Which is also why I run it with -d which keeps it in foreground and this goes to stdout/stderr instead of a file. I keep everything I can in foreground. I can have multiple sessions open and just CTRL-C anything.
Depends on what I do with it. Usually the only noticeable drain is WiFi being active.
But for example encrypting and compressing large files will absolutely toast the phone.
The errors can be a problem, even if they aren’t written to a file. For example with tinyproxy. Disconnecting the network interface it’s running on won’t shut it down, it just keeps producing errors and clearly doing something as it can really heat up the phone.
This is what it spits out (as fast as it can):
Which is also why I run it with
-dwhich keeps it in foreground and this goes to stdout/stderr instead of a file. I keep everything I can in foreground. I can have multiple sessions open and just CTRL-C anything.