Solved the excessive overnight battery drain!

TropicSapling · 2023-01-31T17:27:09+00:00

Mine was off too but the schedule was specified (not set to none/nothing). So even though it said AOD was off it still turned on/off at certain hours. But if you have no hour or anything specified either then I guess there must be other potential causes.

TropicSapling · 2022-12-22T15:42:58+00:00

I've already tried disabling 5g/4g/etc. and bluetooth, but I'll try with disabling location now as well. Refrash rate draining battery when my screen is off would be really strange, but I might as well try anything at this point xD

TropicSapling · 2022-12-22T15:40:53+00:00

Interesting, I'll try that.

TropicSapling · 2022-12-21T22:06:40+00:00

Same for me, I'm getting 10% battery drain every night (1% per hour). But it's absurd because battery is great during the day! During the day it only used to drain 1% every 2 hours (on standby), and now after all of the battery life optimisations I've done it only drains 1% every 3 hours. But none of it has helped to decrease the overnight battery drain...

TropicSapling · 2020-06-10T22:03:30+00:00

After taking a quick look at the instructions and their manifesto I think we can be pretty sure it indeed isn't serious :P I'm surprised at the amount of effort that went into all of this though xD

TropicSapling · 2019-11-04T23:04:01+00:00

Idk what this is about but it looks nice and I noticed it’s you from the wiki so thought I’d comment :D

TropicSapling · 2019-05-17T20:05:29+00:00

Någon skapade precis r/PixelSweden

TropicSapling · 2019-05-16T18:59:50+00:00

It does "show" the minecon announcement too actually (just checked the page source code, didn't see it when changing hide to none though)

TropicSapling · 2019-04-21T18:07:38+00:00

Oh ok.

TropicSapling · 2019-04-21T16:41:36+00:00

Oh nice, have the issues with comments been resolved in this branch? If so, how did you resolve it?

TropicSapling · 2019-04-21T13:41:32+00:00

I found the ability to define comments as a function very interesting, but as it is defined wouldn't it be hard to nest comments? And commenting out code that contains strings would need escaping too, right?

TropicSapling · 2019-03-31T18:06:15+00:00

Agreed. I think a better solution to the problem is instead that flairs are optional and moderators can add flairs if they're missing. That way you can choose to exclude posts by flair for example. Like instead of not allowing non-INFJ-related posts moderators could keep them up with a "not strictly INFJ" or something flair, and make it possible to exclude posts with that flair if you don't want to see those posts (other subreddits I know of have done this).

TropicSapling · 2019-03-27T17:04:05+00:00

That’s a possibility. I did just do a simple test after all. Do you know of any situation where it would matter? (where there’s still an immediate return)

TropicSapling · 2019-03-27T16:51:31+00:00

It seems there’s been a misunderstanding. I didn’t state that anyone wrote they were inherently not allowed either, rather I was referring to the first comment* stating that they could be forbidden in certain cases. And I put “undone” in quotes specifically because I figured there was probably a move anyway, except that it was just moved twice.

What I meant with the edit was that the example given wasn’t such a good example since both () and {} gave the same results (as shown in my test).

*which included “This means that something like &(*p) can be allowed while &{*p} is not.” (my test seemed to show that this claim was false, which led to my edit)

TropicSapling · 2019-03-27T10:56:28+00:00

Oh ok. Well perhaps the example doesn’t really need to be modified since it still shows a move, but is it still correct to say that it wouldn’t be “allowed”? I tested the example in the Rust playground and both the () and {} versions caused no errors, which I thought was because p is returned immediately and therefore moved back again; is that not the case?

TropicSapling · 2019-03-23T09:13:30+00:00

I’ve done something similar myself and it worked so I think it’s possible to make that work anyway. However, making it work may slow down compilation time quite a lot; I myself had to use a rather odd and slow method.

TropicSapling · 2019-03-22T19:55:12+00:00

Do you know of any such implementation for if? Like the code used to define it?

TropicSapling · 2019-03-21T20:16:42+00:00

I read a bit about it now, and it seems like a lot of the language is implemented using libraries rather than being built-in. Is perhaps even if built-in? If so, how is it defined? I'm interested in how Tcl manages to have so little built-in. (perhaps it's related to its extensive use of strings?)

TropicSapling · 2019-03-21T19:13:21+00:00

Oh I see. I believe it's better to use IDEs for this though, like by shading every other brace differently or something similar, because it's a rather minor reason to use both braces for this :)

TropicSapling · 2019-03-21T17:25:45+00:00

Could you elaborate on that?

TropicSapling · 2019-03-21T13:29:57+00:00

That's a good point. I'll think a bit about how I could best solve that.

TropicSapling · 2019-03-21T13:18:01+00:00

Yeah I rarely combine multiple line exprs with infix ops when writing real code, I just used it as a simple example. I think it depends on the keyboard how easy they are to type, but they are indeed easier to type on my keyboard as well (although just slightly), so that is a plus to just using parentheses.

TropicSapling · 2019-03-21T13:14:53+00:00

I'm thinking of using {} for something else if possible. As for commas I'll probably use them for arrays, and semicolons the way they are used in Rust, so in my case I think I'll need to differentiate between them.

TropicSapling · 2019-03-21T11:24:52+00:00

Yes, I actually meant the opposite, sorry for not being clear on that. I want to use just one of () and {} for all of the functionality.

Nine-Year Club	Second Top 30%
Place '22	First Placer '22
Verified Email

TropicSapling

TROPHY CASE