[Wear OS Software and Hacking General] Nazo:
The problem has been more fundamental for me. The underlying voice handling system itself has been screwing up. And there's no nicer way to put it than screwing up. It will show text on the screen that exactly matches what I said and then do something else entirely. But the biggest problem along those lines was it was so overloaded it would take forever to start. If I said "turn on bedroom lights" it would think I only said "lights" and turn on every single light configured through Google Home instead of just the ones I specified. Using a different widget or whatever wouldn't have helped since it was the underlying handling of voice itself that was failing (due, I assume, to it simply struggling that much to even start the process.)

But if you're not seeing the massive all around lack of performance you're not having the same problem. You'd surely notice if every single aspect of every system is more sluggish and less responsive, so you somehow haven't had the same problem as me. Which is weird really. I'm not sure why mine would be doing it if others aren't...

Of course, but the thing about how this sort of tech goes is that a more powerful CPU can still be more efficient if it's of a newer generation. Of course, just being newer doesn't make it so, but it's clear the TicWatch E doesn't use the highest quality CPU ever made. I'm betting a low end MediaTek or something.

It's worth noting that "more powerful" versus "more efficient" is trickier than you may think. If you underclocked the CPU to 10% of its original speed it might generally have better battery life, but it would also work at 100% about ten times more often and ten times longer and the difference might be a lot less than you might think -- or even actually worse depending on what the watch has to do. There's a balance to be struck. A faster CPU gets tasks done more quickly, so if it doesn't use a lot more power to do it it can actually end up being more efficient even just from that alone. Assuming you're not overriding the CPU governor with one that forces it to use more power that is.

Wait, what? Are you using your watch excessively heavily or something? It should last at least a good 10 hours of heavy usage. I use the always on display with a fairly efficient watchface (lots of black, some small dark red areas and the rest a gray instead of pure white) and use it fairly lightly (mostly just as a watch and a way to see notifications and respond to texts while checking the weather or etc once in a while) and mine can probably go a good 20 hours or so between charges while being used this way. Mind you, I turned off the shake to wake gesture since I move my hands around a lot and it would be constantly waking up with that, so most of the time the watch is still downscaling the processor and all despite the partially on screen. (I just wish I could raise the ambient screen's brightness a little bit. Just one notch more so I could see it a little bit in the daylight when I'm outside.) The way I use it my watch goes down less than 3% per hour, so it could easily last a good 33 hours or so. I can't even begin to imagine having to charge twice a day.

Thanks for the list, I appreciate it. Too bad this will all be gone the next time I have to do a full reset (I really wish Android didn't require a full system reset where it has to update everything again, reconfigure everything, etc etc every time, but I sometimes change my phone's ROM and have broken a couple of phones I'm sad to say and each time I had to completely reset my watch and start over on it.) Hopefully I won't have to any time soon, but needless to say I'm bookmarking this thread...

Take a look at the custom watchfaces out there. I'm particularly fond of Pujie Black which has some decent builtin options to start from and then customize from there. I have had people almost daily say my watch looks really nice. (Of course it probably helps that it has that always on screen versus most of theirs being off normally.) There is also at least one really good free one (I've forgotten its name, sorry. I think if you search for "watchface designer" or something like that you'll find it quickly enough.) Mind you, I don't think the builtin watchfaces particularly bog the system down or anything anyway. It's definitely that TicSystem app above all else that was doing it for me and even though I haven't really been using my watch today it seems like every single process (even just swiping on the screen) has been significantly better in handling. So disabling the stock watchfaces probably wouldn't help a lot anyway.